Ignite for Developers

The Developer's contribution to the database performance optimization effort is often underestimated and misunderstood. The developer's role not only includes the design and development of application code, but the ownership of that code, and its interaction and impact on other applications placing demands on the database. In order to remain fully empowered to account for the influence of their application code, Developers need full insight into that influence, at a level detailed enough to take action.

Knowing Your Application Impact Outside of the Testing Arena

One of the most common challenges Developers face is dealing with application code that performs ideally in a testing environment yet creates database bottlenecks in a staging or production environment. Without quantifiable data on which application requests are delayed and why, Developers are forced to rely on inefficient trial-and-error methods to solve the problem. Ignite's Wait-Time approach to analysis measures the amount of time the database spends waiting on each Oracle resource, providing detail down to the SQL statement level. By isolating bottlenecks inside the database layer, Developers can quickly see where meaningful improvements can be made.

Clear Results

For Developers to make changes in application code that support database performance in a production environment, they need performance information that is relevant to their development environment. Ignite identifies bottlenecks caused by each SQL statement and visually represents the results in clear, concise graphics. Developers are empowered with precise data and can directly address the appropriate application code.

Eliminate Finger-pointing Over Problem Ownership

For Developers working in a complex enterprise, solving performance problems requires first determining who is best equipped to fix it. When DBAs, developers, application owners and outside vendors all have a stake in the application, finger-pointing to re-direct blame and responsibility typically results. Ignite gives Developers a definitive tool to identify the root cause of a problem and clearly demonstrate if, when, and how the application is contributing that problem.

Common Language Between Developers and DBAs

While the efforts of Developers, DBAs, IT Managers and outside vendors ultimately serve the same goal of optimizing the experience of the customer, they don't often rely on the same metrics or processes to drive results. Relying on different gauges and indicators results in controversy over the priority and origin of performance problems and who should fix them.

Ignite measures performance using Wait-Time as the primary metric, so all activity is evaluated based on how it affects end user response time. In the past few years, leading books, courses and consultants have all pointed to Wait-Time analysis as the best practice for performance tuning. By ranking performance problems based on the service impact to the customer, Ignite provides a common set of graphical indicators that give all departments involved instant, "actionable" answers about how to improve database performance.

	Challenges Faced By Developers Ignite Benefits Application works fine in test but performs poorly in staging and production environments Delays identified down to the SQL query level, revealing production environment delays, if applicable. Lack of SQL Server specifics makes it hard to pinpoint where to make improvements that optimize code Clear graphs and charts clearly communicate where application code improvements should be made. Ambiguous data about source of performance problems Irrefutable evidence of problem origination Varied gauges and indicators between Developers and DBAs cause controversy over sources of database performance problems. Graphical methods that rank problems based on Wait-Time impact enable clear communication about issues.