Performance Measurement tool

As a developer, you can use the Performance Measurement tool to gather performance data on a running application to help you identify any performance bottlenecks. You can use this tool in both your development environment to test operation performance, and in your production environment to analyze the actual performance of an operation. When you run this tool, you can generate different reports to help you identify operations that impact performance and determine how to improve caching performance.

The Performance Measurement tool is a flexible measurement tool that you can use in the following ways:
  • As a serviceability tool, which you can use to evaluate what the system is doing. This evaluation can be done while the operation runs in the production environment.
  • As a general performance measurement tool, which you can use to determine where time is spent during a request execution.
  • As a cache potential measurement tool, which you can use to determine the value that caching could bring to various operations.
When you run this tool, you can generate any of the following types of reports to help you measure and analyze your site performance:
When this tool runs, it uses API classes to gather metric data for operations to use for generating the preceding reports. The API classes that the tool uses to gather the metrics are built on the Java Logging mechanism. These API classes create a metric gatherer and then create objects of a type OperationMetric. The tool uses these objects to gather the following information about a single operation execution:
  • Start time
  • End time
  • Duration
  • Result size
  • Name
  • Key-value pairs. (that are used as a unique cache key)
  • Whether caching is enabled for the operation
  • Whether the operation result is fetched from cache.
  • Unique ID of the request
  • Unique ID of the parent request
For more information about how to run the Performance Measurement tool to generate reports, see Using the Performance Measurement tool


Depending on how you set up caching for your site, some operations that you cache can use sensitive information as key-values. For example, a servlet login form request might include a user password as a parameter. In this case, the parameter value is typically masked to prevent the value from being included in any generated performance logs.

When you run the Performance Measurement tool, the tool does capture parameter values for select statement within "GET" operations. If the parameter values that contain sensitive information are masked, the generated Performance Measurement tool reports should not include any sensitive information.