Back to Blog

Open LoadRunner Analysis Graphs with Custom Granularity

Is there a way to set the Analysis Tool to open new graphs with a custom granularity? For example, LoadRunner may open all graphs with the granularity set to 300 seconds. Is there away to set it to 10 seconds?

Solution

Create a user-defined template for the Analysis tool. There is no way to set the same granularity to all graphs in Analysis once the result set has been processed. However as a work-around, create and use a user-defined template.

  1. Open a result set in Analysis.
  2. Open up all sets of graphs.
  3. In each graph, set the granularity you want (i.e., 10 seconds).
  4. Choose Tools -> Templates -> Save as template.
  5. Clear the “Use automatic granularity” checkbox.
  6. Select the “Automatically set to new result” checkbox. As a result, each new result set will be opened with the above graphs and granularity desired, with the exception of the Throughput graph. For the Throughput graph, the minimum granularity is 5 seconds by the product design. The reason for it is to avoid too much overhead.

If you would like to set it to a lower value (not recommended due to overhead), here’s what you can do (before you run your scenario):

Note: Please back up your files before any modification.

  1. 1. Open the default.cfg file of the script using a word editor. In the [WEB] section add one more line:[WEB]WebGraphsAggregation=n where n is the number of seconds for graph aggregation.
  2. Open throughput.def in the bin\dat directory using a word editor. In the [Granularity] section, comment out “BaseGranularityUIName” by putting a semicolon at the beginning of the line: Example:[Granularity]
    Dimension=Scenario Elapsed Time
    ;BaseGranularityUIName=Throughput
  3. Open Result0_Graph2.def in \AnalysisTemplates\DefaultTemplate1 using a word editor. In the [Granularity] section, comment out “BaseGranularityUIName” by putting a semicolon at the beginning of the line: Example:[Granularity]
    Dimension=Scenario Elapsed Time
    ;BaseGranularityUIName=Throughput
  4. Save the changes and rerun your scenario.
Back to Blog