Drop absolute p95 latency threshold from benchmark

The p(95)<2000ms gate was calibrated for a single VU. At 50 concurrent
VUs the CI runner saturates and P95 always exceeds 2s, so the gate
failed every run. Keep http_req_failed and flow_failures as the
correctness gates; latency is now judged via the before/after
comparison in the PR comment.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
loks0nandClaude Opus 4.8 committed 2026-06-26 15:44:11 +01:00
1 parent 2face3c292
commit 11397dcba0
1 file changed
-1
-1
View File
@@ -40,7 +40,6 @@ export const options = {
},
thresholds: {
http_req_failed: ['rate<0.05'],
appwrite_api_duration: ['p(95)<2000'],
appwrite_benchmark_flow_failures: ['count<1'],
},
};