When a load test uses parameters from multiple files, Performance Testing Service (PTS) aligns rows across those files using a benchmark parameter. The benchmark parameter file determines row alignment and data consumption order. Reading behavior also depends on whether the test runs in virtual user mode or requests per second (RPS) mode.
How the benchmark parameter works
When an API uses parameters from multiple files with different row counts, PTS assembles data rows based on the benchmark file. The benchmark parameter controls two behaviors:
| Behavior | Description |
|---|---|
| Row alignment | PTS reads as many rows as the benchmark file contains. Other files cycle to match. |
| Use once | When a parameter is set to be used once, that file becomes the benchmark parameter. |
Configure the benchmark parameter and the use-once option in a pre-testing session on the Scenario Settings tab.
Marking a parameter as used once automatically makes it the benchmark parameter. If a benchmark parameter is already set, you can also specify whether to use the parameter once.
Small file as benchmark
PTS reads all rows from the smaller benchmark file and only uses the corresponding rows from the larger file. Remaining rows in the larger file are skipped.
Example: File A (benchmark) has 3 rows. File B has 5 rows. PTS reads rows 1, 2, and 3 from both files. Rows 4 and 5 in File B are never used.
Large file as benchmark
PTS reads all rows from the larger benchmark file. When the smaller file runs out of rows, PTS recycles it from the beginning until the benchmark file is fully consumed.
Example: File A (benchmark) has 5 rows. File B has 3 rows. PTS reads all 5 rows from File A. For File B, PTS reads rows 1, 2, 3, then wraps back to row 1 and row 2 to match the 5 rows in File A.
Virtual user mode
In virtual user mode, each virtual user reads a new data row and sends a new request only after completing the current request (including receiving the response or reaching a timeout). Each virtual user processes one request at a time, so faster responses lead to faster parameter consumption.
Reading with a small benchmark file
Reading with a large benchmark file
RPS mode
In RPS mode, PTS evenly sends a fixed number of requests per second based on the current load value. The number of virtual users adjusts automatically:
Faster response times require fewer virtual users to sustain the target RPS.
Slower response times require more virtual users.
The benchmark parameter and row alignment logic work the same way as in virtual user mode.
Reading with a small benchmark file
Reading with a large benchmark file
