JDBInsight 2.5 "Trace in Time" is now available for immediate download. This new release focuses on the timeline analysis of transaction and SQL statement executions allowing for the immediate identification of performance bottlenecks as a result of concurrency issues at the database or resource transaction manager level.
[Production Ready] JDBInsight 2.5 has undergone many performance enhancements ensuring it has the lowest overhead of any performance management solution on the market while providing more indepth analysis than a typical Java profiler or transaction trace analyser.
[10x Better] In a recent customer product evaluation, JDBInsight had 10 times lower overhead (5% versus 50%) than a similiar J2EE server tracing tool while providing 10 times more contextual information at a price 10 times less expensive (5,000 vs 50,000 USD).
JDBInsight 2.5 offers the ability to capture detailed profile data of the transactional execution behaviour of a J2EE/Java/JDBC application. The benefits in trace timeline analysis are:
Transaction/SQL Concurrency: With timeline information a performance engineer can detect whether performance slow downs occur under a certain level of heavy concurrency for particular transactions patterns or SQL statements. It is also possible to correlate high maximums for both transactions and SQL statement with other events or processing occurring within the servers JVM such as garbage collection, waiting and blocking.
Database Bound Transactions: Tracing provides a visual clue of the Java code execution periods within a transaction that do not contain database activity. This helps a performance engineer understand whether a transaction is database bound or has other computational work being performed within the transaction period. With the timeline graphs engineers can determine what parts within the transaction period result in slow downs (long periods of non-JDBC activity) without the performance impact typically associated with Java code profilers.
Sub Transaction Analysis: The transaction timeline graph helps identity resource transactions nested (in terms of timeline execution) within another resource transaction execution period. Nested transactions create additionally server resource requirements because of the need to utilize extra connections during the suspension of outer transactions. This suspension also results in the low utilization of connections resources. For EJB applications it can result in extra entity bean instances being instantiated, loaded and stored that have previously being accessed in an outer transaction or adjacent child sub transactions.
Debugging: The tracing data includes system generated object ids for JDBC resource instances allowing for debugging of transaction executions at the instance level. This data can help determine what particular instances are being invoked on and whether object instances are closed explicitly within the transaction they were created in. The tracing data records creation points for instances (the result column) as well as close method calls (the target column). Additionally exceptions are associated with instances instead of methods or call stacks provided by other tools.
Read the Chapter 9 - Tracing from the JDBInsight User Guide [click here]
View the JDBInsight 2.5 "Trace-in-Time" Flash Demo to see the user interaction with tracing profile data [click here]
Installers are available for Windows, Solaris, and Linux with native agents for HP-UX and AIX platforms. [click here]
"J2EE tuning, tracing and testing with Insight"http://www.jinspired.com