iStrobe Product Preview

Analyze application performance via a web browser

iStrobe is Compuware's web browser-based product for analyzing Strobe application performance data. iStrobe provides a browser-based view of Strobe performance profiles allowing all levels of IT professionals to quickly and easily measure performance of applications and pinpoint inefficiencies within them. With iStrobe, users can view and analyze Performance Profile information interactively using a standard browser such as Internet Explorer or Netscape Navigator.


Locate application inefficiencies quickly Users can quickly locate application inefficiencies with the iStrobe Top Resource Consumers Report. The report identifies the most resource-consumptive system service routines (CPU, Wait, EXCPs), files and user program statements, allowing you to then drill down directly to detailed reports. Our enhance profile management functionality also includes profile import and profile delete, the ability to create and store profile notes, and resource threshold tailoring by report.	Top resource consumers (click image to enlarge)

Minimize application resource demand The iStrobe Resource Demand Distribution Report summarizes the use of CPU and I/O resources in the measured job step. A histogram provides an easy way to visually identify which tasks were resource-intensive.	Resource demand distribution (click image to enlarge)

Obtain performance improvement recommendations Additional in-depth information on what a module does and how to reduce or eliminate the time spent in the module is available by clicking on the module name. Users can also browse through the Module Help database for detailed system service module descriptions and recommended solutions to improve application performance.

CICS transactions iStrobe reports highlight resource-consumptive CICS transactions, summarizing all components of transaction response time including CPU dispatch delay and suspend time, the number of times a transaction executed, and the average service time. In the example on the right, users can identify how much of the CICS transaction response time is due to MQSeries calls and then drill down for additional, detailed CICS and MQSeries reports.	Resource-Consumptive CICS transactions (click image to enlarge)