The Response Time Hotspots dashlet provides a high-level view of a session to give you a quick impression of where the time is spent. A typical use case is to filter for Business Transactions to see how similar transactions are distributed regarding response time and where most of the time is contributed, by tier and by API.
You can use the filter list in the top right corner of the dashlet to filter the content to the slowest 1%, slowest 5%, slowest 10% or fastest 90% of transactions in the session.
Server transaction statistics
The top area shows the distribution of the PurePath response times. This chart gives a quick impression of the typical response times of the PurePaths. It is recommended to apply a timeframe filter so similar PurePaths are used for this calculation.
Response time formulas
When a PurePath is executed, AppMon captures CPU time used by the threads that are executing this transaction. It also captures the information on how much time was spent in sync (sync blocks), wait (waiting on an object) and runtime suspension (when garbage collection pauses the thread). The rest of the time is contributed by I/O.
The formula for response time therefore is:
Response Time = CPU + Sync + Wait + Runtime Suspension + I/O
I/O is calculated and everything else is measured:
I/O = Response Time - CPU - Sync - Wait - Runtime Suspension
HotSpots by tier
This chart shows either the top five Agents or the top five Agent Groups sorted by the response times of the PurePaths executed there. Clicking a bar opens the Method Hotspots Dashlet dashlet showing the methods that contribute most to the PurePaths executed on this Agent or Agent Group.
HotSpots by API
The Hotspots by API chart shows the times spent per API. Clicking an API opens the Method Hotspots Dashlet dashlet showing the methods by their contribution to that API. Clicking a database-related API opens the Database Dashlet dashlet.