You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/performance.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ This page is intended to provide clarity on how to obtain the benchmark numbers
20
20
## Methodology and Infrastructure checklist
21
21
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:
22
22
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.
24
24
25
25
- 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.
0 commit comments