From dda7a4f26b58a6eb7bf73af18b26d9220b5a2e93 Mon Sep 17 00:00:00 2001 From: Aqua Date: Sat, 7 Nov 2026 05:33:49 +0000 Subject: [PATCH] spike: README reports 74 of 400000 as a single run's figure Co-Authored-By: Claude Sonnet 5.5 --- spikes/faust-aot-thruster/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spikes/faust-aot-thruster/README.md b/spikes/faust-aot-thruster/README.md index 6d34f5b..6cad95b 100644 --- a/spikes/faust-aot-thruster/README.md +++ b/spikes/faust-aot-thruster/README.md @@ -28,7 +28,7 @@ median 0.052 ms (0.49% of the 10.667 ms deadline), p99 0.08-0.16 ms (~1-1.5%). C median 0.052 ms, p99 under 0.16 ms. The host's tail is not judgeable (see below). **Max block time: UNEXPLAINED. It is not a pass.** Max was 10.8-17.1 ms, with 1-5 of 20000 blocks over -the deadline per run (400000-block `process` runs: 70-74 over; see the control below). What the instrumented runs (`run.sh`, `CORE=` pins with +the deadline per run (400000-block `process`: 74 over in one run, core 3; see the control below). What the instrumented runs (`run.sh`, `CORE=` pins with `taskset`; every overrun prints a `wall_unix` timestamp, wall ms and thread CPU ms) do show: - Not per-block DSP cost: `NOOP=1` times a 0.05 ms busy-wait instead of `process`, and stalls about the