Proof
Disconnected DevTools overhead
Baseline and candidate measurements for the diagnostic bridge while no DevTools listener is connected.
v0.1.0-devAdvanced
Disconnected DevTools overhead
One focused experiment compared identical core copies before and after the automatic diagnostic bridge, with no extension listener connected. Each value is median nanoseconds per Command; ten full-profile samples ran on the same Apple M1 system.
| Mode | Scenario | Baseline | Bridge candidate | Difference |
|---|---|---|---|---|
| JIT | one Command and one State | 2,760.17 | 2,756.35 | -0.14% |
| JIT | 10,000 sequential updates | 2,745.39 | 2,765.11 | +0.72% |
| JIT | 100,000 sequential updates | 2,770.92 | 2,765.35 | -0.20% |
| AOT | one Command and one State | 2,785.79 | 2,765.90 | -0.71% |
| AOT | 10,000 sequential updates | 2,792.92 | 2,767.87 | -0.90% |
| AOT | 100,000 sequential updates | 2,777.51 | 2,781.45 | +0.14% |
The largest measured regression was 0.72%, below the experiment's 3% acceptance threshold. Changes point in both directions and do not show a persistent disconnected slowdown.
This result does not say connected DevTools is free. Active event encoding, serialization, transport, and UI work add cost and were outside this experiment. Product VM and web builds compile the bridge out.