Skip to content

Commit 4333eef

Browse files
authored
Update the Performance Tests doc (#2496)
1 parent d5b4050 commit 4333eef

1 file changed

Lines changed: 11 additions & 11 deletions

File tree

tests/performance/README.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -15,27 +15,27 @@ Performance tests measure the response time overhead of the Serverless serving l
1515
make install-monitoring
1616
```
1717

18-
2. Forward the Grafana port to localhost:
18+
2. Forward the Grafana port to localhost in a separate terminal:
1919

2020
```bash
2121
make forward-grafana
2222
```
2323

2424
## Running the Tests
2525

26-
1. Run the full test suite three times to collect enough data for averaging:
26+
Run the full test suite three times to collect enough data for averaging. Each run tests all runtime/profile combinations sequentially and runs in the background, so it may take a while to complete.
2727

28-
```bash
29-
make start-test
30-
```
28+
```bash
29+
make start-test
30+
```
3131

32-
2. Follow the progress in a separate terminal:
32+
Optionally, follow the progress (this step can be run in the same terminal):
3333

34-
```bash
35-
make follow-remote-test
36-
```
34+
```bash
35+
make follow-remote-test
36+
```
3737

38-
Each run tests all runtime/profile combinations sequentially.
38+
You can also monitor progress in the Grafana dashboard by opening the **Serverless Performance Tests** dashboard at `http://localhost:3000`. See [Collecting Results](#collecting-results) for steps on how to export the data.
3939

4040
## Collecting Results
4141

@@ -52,7 +52,7 @@ After collecting CSVs from three runs, update `docs/user/00-50-limitations.md`.
5252

5353
You can use an AI assistant such as Claude Code to automate this step. Example prompt:
5454

55-
```
55+
```bash
5656
claude "Update the performance test results in docs/user/00-50-limitations.md based on the CSV files: <path1.csv>, <path2.csv>, <path3.csv>. Recalculate averages across all runs (exclude outliers if a single value deviates more than 3x from the others). If any runtime/profile combination shows a significant error rate, note it in the document — use your judgement on what constitutes a significant error rate. Also update the node specification in the NOTE if it differs from the current cluster — check it with: kubectl get nodes -o wide and kubectl get nodes -o jsonpath='{.items[0].status.nodeInfo.kernelVersion}'. Update the test run count and last updated date accordingly."
5757
```
5858

0 commit comments

Comments
 (0)