Terminal echo confirmation p99 exceeds RTT plus two frames at 300 ms

kayg commented

2026-10-07 08:10:02 +00:00

Owner

Finding from the D130 latency run on branch latency-gate at base cecc7ecd7b. Reproduce with TRACER_TEST_PORT=4621 bun x playwright test test/terminal.spec.ts --grep "first run, passkey login". This ran the built tracer through the test TCP proxy at RTT 300 ms, jitter ±30 ms, loss unsupported for the reliable TCP stream.

METRIC name=keystroke_echo_confirmed source=tracer-production-build n=20 p50_ms=323.90 p99_ms=338.00 budget_ms=334 result=FAIL
METRIC name=keystroke_glyph_visible source=tracer-production-build n=20 p50_ms=330.80 p99_ms=357.20 budget_ms=17 result=REPORT
The glyph metric is report-only until predictive echo #50 lands. The echo confirmation budget is RTT + 2×17 ms. Proxy self-test nearby measured configured RTT 300 ms / jitter 30 ms at p50 307.72 ms, p99 335.84 ms. Host infraternal-dev, Linux x86_64, 8 cores; load average during run was 10.19/10.22/8.16. Product changes are outside #55.

Finding from the D130 latency run on branch latency-gate at base cecc7ecd7bb452229fcf292bebde0917c0568522. Reproduce with TRACER_TEST_PORT=4621 bun x playwright test test/terminal.spec.ts --grep "first run, passkey login". This ran the built tracer through the test TCP proxy at RTT 300 ms, jitter ±30 ms, loss unsupported for the reliable TCP stream. METRIC name=keystroke_echo_confirmed source=tracer-production-build n=20 p50_ms=323.90 p99_ms=338.00 budget_ms=334 result=FAIL METRIC name=keystroke_glyph_visible source=tracer-production-build n=20 p50_ms=330.80 p99_ms=357.20 budget_ms=17 result=REPORT The glyph metric is report-only until predictive echo #50 lands. The echo confirmation budget is RTT + 2×17 ms. Proxy self-test nearby measured configured RTT 300 ms / jitter 30 ms at p50 307.72 ms, p99 335.84 ms. Host infraternal-dev, Linux x86_64, 8 cores; load average during run was 10.19/10.22/8.16. Product changes are outside #55.

kayg referenced this issue

2026-10-07 08:10:06 +00:00

Tests: high latency by default + input-to-photon gate (D130) #55

kayg commented

2026-10-07 08:16:22 +00:00

Author

Owner

Latest run using the finalized 200 ms burst-jitter relay measured keystroke→echo confirmation p50 331.80 ms / p99 359.90 ms against 334 ms. The configured network self-test measured 308.80/324.03 ms p50/p99; machine load was 7.00/7.52/7.43 on 8 cores.

kayg commented

2026-10-07 09:14:43 +00:00

Author

Owner

Updated #55 production tracer measurement on infraternal-dev (x86_64, 8 cores; tracer-browser load 14.31/16.38/15.76), configured RTT 300 ms ±30 ms: keystroke-to-echo-confirmed n=20 p50 345.50 ms, p99 362.20 ms, budget 334 ms, FAIL. The same run reported glyph-visible p50 349.30 ms/p99 368.40 ms (budget 17 ms, report-only until #50). scripts/verify latency, TRACER_TEST_PORT=4621; source apps/tracer/test/terminal.spec.ts; log latency-profile.log in the latency-gate scratch directory.

kayg commented

2026-10-07 09:43:30 +00:00

Author

Owner

Latest production-build profile on infraternal-dev (x86_64, 8 cores; tracer-browser phase load 17.73 10.48 10.96): echo-confirmed n=20 p50=349.60 ms, p99=371.40 ms, budget 334 ms, FAIL. Glyph-visible p50=364.60 ms, p99=381.00 ms (report-only pending #50). See #55 for per-hop attribution and screenshots.

kayg referenced this issue

2026-10-07 10:32:58 +00:00

Tests: high latency by default + input-to-photon gate (D130) #55

kayg commented

2026-10-07 10:32:58 +00:00

Author

Owner

Latest production input probe on infraternal-dev (x86_64, 8 cores; tracer-browser load 8.84/9.29/7.19), 300 ms RTT ±30 ms:
METRIC name=keystroke_echo_confirmed source=tracer-production-build n=20 p50_ms=337.60 p99_ms=364.70 budget_ms=334 result=FAIL
METRIC name=keystroke_glyph_visible source=tracer-production-build n=20 p50_ms=352.10 p99_ms=372.40 budget_ms=17 result=REPORT
Glyph latency remains report-only until predictive echo #50. Full trace output is in the run log and the tracer-probe-results.txt attachment generated under apps/tracer/test-results/.

Latest production input probe on infraternal-dev (x86_64, 8 cores; tracer-browser load 8.84/9.29/7.19), 300 ms RTT ±30 ms: `METRIC name=keystroke_echo_confirmed source=tracer-production-build n=20 p50_ms=337.60 p99_ms=364.70 budget_ms=334 result=FAIL` `METRIC name=keystroke_glyph_visible source=tracer-production-build n=20 p50_ms=352.10 p99_ms=372.40 budget_ms=17 result=REPORT` Glyph latency remains report-only until predictive echo #50. Full trace output is in the run log and the `tracer-probe-results.txt` attachment generated under `apps/tracer/test-results/`.

kayg referenced this issue

2026-10-07 10:55:40 +00:00

Tests: high latency by default + input-to-photon gate (D130) #55

kayg referenced this issue from a commit

2026-10-10 09:20:35 +00:00

Merge latency-gate: 300 ms RTT test profile and input-to-photon gate (#55, D130)

kayg referenced this issue

2026-10-28 17:52:29 +00:00

Tests: high latency by default + input-to-photon gate (D130) #55

~~kayg referenced this issue 2026-10-28 17:53:55 +00:00~~

Orchestrator handover 2026-10-28: moving to a new machine #254

~~kayg referenced this issue 2026-10-28 17:53:56 +00:00~~