Analytic Components
Top level views
.. to get the big picture
… because you cannot know everything at once
Transparent top-level views provide externals, consultants, administrators, and project managers collaborating in large and possibly distributed development teams with the big picture to keep track of things to improve the coordination of tasks.
Layer Breakdown – Timeline
The new dashboard ‘Layer Breakdown’ now provides you with a quick bird’s eye view of the application’s overall time consumption layer by layer, so you can see at one glance where the most time was consumed. It is the ideal management reporting and controlling tool to help testers, consultants, architects and managers to scan the critical areas and check what still needs to be done.
CPU utilization – Timeline
The CPU utilization timeline provides you with an overview of your CPU utilization over time. By pinpointing the resource usage, you can identify time loss due to waiting (low capacity) for long running tasks or time loss due to too much activity (CPU burners, high capacity).
Information-Clustering (e.g. Caller Callee)
Information clustering provides you with a flash bird’s eye view of the application’s overall time consumption and where the load is triggered from.
Timeline Views
.. to capture the details
… because not everything happens at a time
Most profilers only deliver average times and do not provide any information on timing variation – and yet this is absolutely crucial to find the real causes of your issues. Does your application show any peaks in execution times? When exactly and how often did these problems occur? Timeline views provide you with valuable information on the real context of your issues.
Call History – Charting
Call History pinpoints exceptionally high execution times as individual instances of possibly critical operations.
CPU Time Consumption – Partial Analysis
SpeedTrace retains the timeline, so that any analysis can be performed on a particular time range of interest. This helps you to understand why your application performance breaks down at specific times whereas it runs fine most of the time.
Trace Views & Data Context
.. to reconstruct scenarios
… because you need to know the root cause
Call History shows data-related performance problems
Simply identify the root cause of problems by including the data context of operations, for example, by using the names of executed stored procedures.
Better than all line-level information …
Profiling only provides you with statistical information. Tracing enables you to reconstruct the sequence of actions that actually generate any problem.
Interactive Charts & Smart Drilldowns
.. to zoom into the core of your issue
… because you need the right information at the right time
Interactive Charts (e.g. Function View – see first chart below) enable you to systematically map out and structure all the symptoms of your issue (first chart below: Function View), while Smart Drilldowns (following charts below: Caller-Callee, Callstack and Trace Views) allow you to move on from the symptoms to zoom right into the core of your problematic code.
Simplify Complexity
.. to focus your view
… because time to resolve/repair matters
Significantly reduce your analysis time by removing irrelevant information!
When you profile your application, you do not need to include third party software or code that is not yours, in short, anything that is out your reach and cannot influence anyway. Simplify Filters, for example, allow you to eliminate all excess code to streamline your profiling process and further reduce time to repairs.
