Bound adversarial promo-pattern timing at 250 ms (#126) #47

Merged

backmeupplz merged 2 commits from fix/126-perf-test-bound into main

2026-10-15 18:11:30 +00:00

backmeupplz commented

2026-10-15 18:07:13 +00:00

(Migrated from github.com)

The Easypanel deploy build for b726c9a (#44 plus #45) failed matching stays linear on long adversarial input in the Dockerfile check stage. The best warm run of an input was 55 ms against the 50 ms bound. The build host is about 2.5x slower than CI and local machines (the quadratic-ish прошла @abot repeat input is about 20 ms warm locally), so a 50 ms absolute bound is machine-dependent.

The bound is now 250 ms, still best of 3. Injected catastrophic backtracking measured over 5 s on every run (review of #45), so a 20x margin remains on both sides. The doc line is updated to match. This change is test and doc only.

The Easypanel deploy build for b726c9a (#44 plus #45) failed `matching stays linear on long adversarial input` in the Dockerfile check stage. The best warm run of an input was 55 ms against the 50 ms bound. The build host is about 2.5x slower than CI and local machines (the quadratic-ish `прошла @abot` repeat input is about 20 ms warm locally), so a 50 ms absolute bound is machine-dependent. The bound is now 250 ms, still best of 3. Injected catastrophic backtracking measured over 5 s on every run (review of #45), so a 20x margin remains on both sides. The doc line is updated to match. This change is test and doc only.