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
{{ message }}
Repository navigation
Commit 4dea8c4
Browse filesBrowse the repository at this point in the historyBrowse files
fix(box-qualify): pool the floor baseline across the field, it measures the rig not the gateway
direct_c1_p99_us is the load generator hitting the mock with NO gateway in the
path. It describes the rig and the instance type, so keeping a per-gateway
baseline was a category error, and an actively harmful one: with one or two
historical samples each, a gateway's baseline was a random draw from the box
population, so a gateway that happened to draw a fast box rejected perfectly
normal ones while a gateway that drew a slow box accepted almost anything.
Observed live: apisix carried a 73us baseline and was rejected at 77us, a value
squarely inside that same run's healthy spread of 70-80us, while a genuinely bad
box at 89us was correctly caught on a 77us baseline. Same gate, same band,
opposite outcomes, decided by which box each gateway happened to draw months ago.
The floor lane now pools every gateway's snapshots for the arch (window 15,
roughly one full field run's population) and the median describes the population
rather than one lucky draw. The peak lane stays per gateway, because throughput
genuinely is a property of the gateway under test. Verified against the live
snapshots: every gateway now resolves to a 77us pooled floor, apisix's 77us reads
+0.00% and passes, and the 89us box still reads +15.58% and fails.
A new gateway with no history of its own now inherits the field's floor and is
protected from a bad box on its first run, while still seeding its own peak.
0 commit comments