Database Performance:
Traditional tools focus on computer events, such as counter statistics, that may or may not have a bearing on whether your application is performing optimally. Trying to realize results from this type of data can be a fruitless exercise. Your SLAs are not derived from counter statistics. Why should your performance management software be?
Within minutes of its application Ignite helps the DBA zero in on the steps that are causing the greatest delays and drill down to a level of granularity that enables rapid resolution. Database performance gains are significant and immediate. Best of all, these gains come without burning precious staff time or capital for hardware and software license fees. By squeezing greater database system performance out of existing systems, Confio customers have reported near-immediate paybacks on their Ignite investment and ROI levels of 10 times or more.
In the Figure 1 below, the two approaches to measuring database system performance are illustrated. The step consuming time is identified by the red clock.
Transaction environments are, by definition, dynamic. Not only do transaction loads increase over time - happily, of course, for most businesses - but the applications are constantly improved for better customer service. It is this very dynamic that has made Ignite so useful, because when things are in a constant state of change performance problems emerge just as dynamically.
Ignite eliminates the trial and error approach that typically follows when Database Performance issues are raised. It also helps to eliminate the finger pointing among peers and vendors that can result when identifying the source of the problem proves elusive.
Helping customers avoid unnecessary human effort and capital expense has been rewarding for Confio. Yet, at the same time they have long recognized that in today's complex three-tiered transaction environments the database performance is not the sole province of bottlenecks. The Web layer and, particularly, the application or Java layer can both be culpable in slowing down the transaction. That is why we have developed Ignite for Java, to bridge the gap between database and application environment with in-depth visibility into the time consumed by at each layer.
Through years of experience, DBA users have learned that it can be organizationally challenging when Ignite for Oracle points to a database performance bottleneck that is determined to be outside of the database itself.
For example, Figure 2 illustrates the typical scenario where system administrators, DBAs and application owners all focus on their individual functional area, but there is no cross-system collaboration.
What is needed is an end-to-end database solution that gives everyone who touches on the DOING MORE WITH LESS: transaction environment the power to easily recognize performance bottlenecks wherever they reside and correct them immediately.
The Ignite Suite is designed to find service problems before your users do. It includes the ability to continuously monitor service levels for selected transactions and users and to send alerts, (console messages and emails), when response times exceed pre-determined thresholds. Reporting capabilities capture historical service level information to easily quantify and document SLA compliance.
Database Performance Solution:
Ignite for Java database performance analysis enables the user to drill down deeply to identify individual applications, packages and methods; to unwind the Java call tree, showing method calls and Wait Time at every level; to display Hot Spot charts that show methods creating the most Wait Time and web requests that are impacted; and to continuously monitor real transactions as opposed to synthetic data.
