After a Performance Testing Service (PTS) stress test completes, PTS automatically collects the test data and generates a report. The report covers business metrics, presser (load generator) resource usage, request sampling logs, automated insights, and performance baseline comparisons.
The report helps you answer questions like:
Did the test meet its performance targets?
Where are the bottlenecks -- client side (presser) or server side?
Which API requests failed, and why?
How does this run compare to previous runs?
Prerequisites
Before you begin, make sure that you have:
A completed PTS stress test
Access to the PTS console
Open a report
Log on to the PTS console and choose Performance Test > Reports.
Find the report and click View Report in the Actions column.
Sampling logs are retained for 30 days. After this period, the logs are no longer available. Export and save the report before the retention period expires to avoid data loss.
Report sections
The report contains the following tabs. Each section explains what the tab shows and when to use it.
Business monitoring
Path: Global Monitoring > Business monitoring
Check this tab first after a test completes. It provides an overview of API-level performance, including success rates, response times, and throughput across all scenarios.
The tab displays:
Basic information about the test run
Business metric overview (aggregated across all APIs)
Per-API breakdowns with detailed metrics
For metric definitions, see Test metrics.
Presser monitoring
Path: Global Monitoring > Presser monitoring
Check this tab to determine whether the presser (load generator) became a bottleneck during the test. High CPU or memory usage on the presser can distort test results, making server-side performance appear worse than it actually is.
The tab displays:
| Metric | Description |
|---|---|
| Region | Region where the presser is deployed |
| Network bandwidth | Network bandwidth consumed by the presser |
| CPU utilization | CPU usage of the presser |
| Memory capacity | Memory usage of the presser |
Request sampling logs
Tab: Request Sample Log
Inspect individual request and response details to diagnose specific failures, such as unexpected status codes or slow responses.
To view a log entry:
Click the Request Sample Log tab.
Find the log entry and click View Details in the Actions column.
Review the request and response on the General tab, or examine timing breakdowns on the Timing Waterfall tab.
Insights
Tab: Insights
Review an automated summary of the test results. PTS evaluates the collected data and highlights potential issues, making it faster to spot problems without manually reviewing every metric.
Performance baseline comparison
Tab: Performance Baseline Comparison
Compare test results against predefined performance baselines. This tab appears only if baseline thresholds were configured when the scenario was created.
For example, if you set the average response time (RT) baseline to less than 1,000 ms and the actual average RT is 3,590 ms, the test is marked as failed.
Scenario snapshot
Tab: Global Snapshot
Review the scenario configuration for the test run, including API definitions, concurrency settings, and other parameters. This is a read-only view; you cannot start a new test from this tab.
Compare reports across runs
Compare reports from multiple runs of the same scenario to track performance trends or validate that optimizations improved results.
Open a report and click the Performance Baseline Comparison tab.
Click Select Report to import other reports from the same scenario.
Review the side-by-side comparison.
You can compare up to three stress testing reports at a time. All reports must belong to the same scenario.
Key metrics
| Metric | Description |
|---|---|
| Request success rate | Percentage of successful requests across all scenarios in the test |
| Assertion success rate | Percentage of successful assertions (checkpoints) across all scenarios in the test |
| Average response time | Average response time (RT) of all APIs, in milliseconds |
| Average throughput (TPS) | Average transactions per second (TPS) during the test |
| Peak throughput (TPS) | Maximum TPS reached during the test |
| Number of error requests | Number of failed requests during the test |
| Assertion failed requests | Number of requests that failed configured assertions or checkpoints |
| Total requests | Total number of requests sent by PTS during the test |