1movmedia/pyworker
2
0
Fork 0
Code Pull Requests Activity

Restructure null pyworker --demo as a clean trapezoid

Browse Source 
Three reservations 30s apart, each with a 90s duration. They end one at
a time, also 30s apart, then the client exits. Each reservation ends
via its duration cap (200 success) rather than the previous "cancel one,
leave two open" pattern that left two 499s pending.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Rob Ballantyne
2026-05-11 18:00:46 +01:00
parent 147bf2597a
commit ef3f34a515
2 changed files with 21 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
workers/null/README.md
+5 -4
View File
@@ -151,10 +151,11 @@ Staggered demo:
python -m workers.null.client --endpoint <ENDPOINT_NAME> --demo
```
Starts three reservations 30s apart (all held concurrently), waits another
30s, then cancels the first by dropping its HTTP connection. The remaining
two run until their duration cap. Useful for watching scale-up and
scale-down behaviour in the autoscaler dashboard.
Starts three reservations 30s apart (all held concurrently) with a 90s
duration each. They scale down one at a time, also 30s apart, then the
client exits — a clean trapezoidal load curve for watching scale-up and
scale-down in the autoscaler dashboard. Each reservation ends via its
duration cap (a 200 success in metrics).
## Notes and caveats