Here are a number of tricks to cut down effort required for making Analysis data available with HP Performance Center. I realized,that some of these are not known when talking to colleagues who have been working with Performance Center for a while. I decided to collect them here… Hopefully it will be a benefit for some of you.
Opening analysis data
Downloading raw result files from the Performance Center to open the results in Loadrunner Analysis is cumbersome (consider download time, unzipping, and then waiting for your desktop to produce the charts). Just like HP Loadrunner Virtual User Generator (VuGen), also the Analyis tool can be connected directly to the Performance Center, so the desired test results can be opened via the File/Open function. However it is only available if the results have already been analysed by the Performance Center.
Get Performance Center to analyse the test
It is practical to let the Performance Center do the majority of the work for calculation of test results.
- This saves time if the Performance Center is running on a more powerful machine than the tester’s workstation.
- Also the volume of downloaded data is substantially less than downloading the raw results.
- Analysis data will be available right from the Performance Center User interface (results.html at the test results view), so the Analysis desktop app will not be needed to take a first glance of the test results.
Automate analysis process
There are several ways to start test analysis on the Performance Center user interface.
The most common is to activate the „Analyse” button in the Currently Running test view.
I am in the habbit of running overnight tests, and I like to start the morning looking at the fresh results, instead of waiting for the long process of the Analysis to run.
The test can be configured to automatically start analysis when the test is finished. See the screenshots below.
If the test is scheduled (rather than started manually), automatic analysis can be configured as seen below.
Reduce data volumes
In the course of a long-running stability test the collected raw data volumes can grow massively. This makes the analysis especially long-winded. For stability testing, exact results (e.g response times, resource usage) are usually not vital. So the sampling frequency can be lowered to cut down the amount of collected raw data. This can be configured in the Performance Center Options pane. Here I have set 60 seconds sampling rate (instead of the defult 5 and 3 seconds).
I hope these tips help you save time and unnecessary coffee breaks.