forked from mtusi2026/mtusi2026lab3
The k6 profile from the prepared kit runs an open model against the balancer from the edge network: constant arrival rate, 80 % keyed message posts and 20 % history reads over 20 synthetic users and 10 chats, metrics only for the measure phase, and no setup data (tokens) in summary.json. scripts/k6.sh runs it with the host uid so the summary is writable on Linux too. scripts/probe.py gains three things. check --rounds repeats the same-key race with a new key per round and counts rounds with identical bodies, one stored copy and 409 on another body. load runs an action under k6 while a probe posts every 0.1 s and resends the same key after a failure and a poller reads the number of UP servers; it writes the action log, the probe and LB traces, the delta of the backend retry, redispatch and error counters, and a verdict: dip for a replica that leaves and returns, replace for a rolling update that must keep capacity and end on new replicas only. detect runs the action in the background and polls the balancer at the same time, so a drain that ends after the exclusion is visible, and checks the declared maximum, the LB answer after detection and the time to restore. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>