mirror of
https://github.com/BerriAI/litellm.git
synced 2026-09-16 23:41:43 +00:00
5f17261534
CLIENT PAUSE ALL for the length of the chaos phase instead of CLIENT PAUSE WRITE, so every Redis touchpoint on the request path times out rather than just the writes. The pause is sized to the phase because it freezes the control connection too; teardown's CLIENT UNPAUSE is a safety net for a phase that overran Latency, RSS and CPU are now budgeted as chaos-over-baseline ratios (p50/p90/p99 for latency and RSS, CPU seconds per request once) through a small phase_budget module, replacing the machine-shaped absolutes. The Redis timeout rate is reported but no longer asserted The final /metrics scrape waits for litellm_deployment_failure_responses_total to stop moving, since that counter is bumped from the async logging queue and lagged the load generator by thousands of increments. The model group carries a unique marker so a deployment left behind by an aborted run cannot absorb this run's retries Co-Authored-By: Claude Code <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| conftest.py | ||
| load_client.py | ||
| locust_load.py | ||
| locustfile.py | ||
| phase_budget.py | ||
| proxy_usage.py | ||
| session_anomaly.py | ||
| test_locust_load.py | ||
| test_phase_budget.py | ||
| test_proxy_usage.py | ||
| test_redis_chaos_e2e.py | ||
| test_session_anomaly.py | ||
| test_weekly_session_anomaly_e2e.py | ||
| weekly_anomaly_config.yml | ||