Skip to content

Commit 8506633

Browse files
committed
small fix
1 parent 2d35cdf commit 8506633

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/performance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ This page is intended to provide clarity on how to obtain the benchmark numbers
2020
## Methodology and Infrastructure checklist
2121
As stated previously we encourage the community to run the benchmarks on their own infrastructure and specific use case. As part of a reproducible and stable metodology we recommend that for each tested version/variation:
2222

23-
- Monitoring should be used to assert that the machines running the the benchmark client do not become the performance bottleneck.
23+
- Monitoring should be used to assert that the machines running the benchmark client do not become the performance bottleneck.
2424

2525
- A minimum of 3 distinct full repetitions, and reported as a result the median (q50), q95, q99, overall achievable inference throughput, and if possible ( and recommended ) the referral to the full spectrum of latencies. Furthermore, benchmarks should be run for a sufficiently long time.
2626

0 commit comments

Comments
 (0)