BACQM Systems Research Group · Instrumentation
Measured, not assumed
Every figure on this site comes from instrumentation at the kernel–hardware interface, under real work. Differences are taken against a baseline that is the same kernel with nothing of ours loaded (E1); shapes are taken on the deployed system itself (E2–E4). The probe never adds load to flatter itself: what the system does while it is observed is what it does.
E1A/B campaigns against the baseline
Protocol. CONTROL is the unmodified kernel with its default fair scheduler. Each campaign alternates CONTROL and BACQM on the same node, runs per arm, and reports the median. A campaign counts only if the thermal state stays within 5 °C across its runs; two campaigns failed that test and are excluded.
| Quantile | BACQM against CONTROL | Basis |
|---|---|---|
| p99 · p999 · max | −90 % to −99 % | 8+ A/B campaigns, each |
| p50 | +10.5 % to +13.8 % | same campaigns |
The median rises a little and the tail collapses. That is a declared Pareto choice of the scheduler's architecture, not a tuning artefact: the tail is where a saturated system fails.
E2Passive telemetry, weekly
Probe. Every 30 minutes, under normal use and with no synthetic load, a 5-second probe measures the wakeup delay of a periodic 1 ms thread. 2,582 samples with the scheduler active, 15 Aug – 14 Oct 2026.
Wakeup delay, weekly medians
µs · passive_weekly_medians.csvTable view
| ISO week | samples | p50 | p99 | p999 | max | missed |
|---|
| Interval | Samples | p50 | p99 | p999 | max | Missed cycles |
|---|---|---|---|---|---|---|
| 15 Aug – 26 Sep | 1,791 | 83.3 µs | 119.8 µs | 317.0 µs | 513.9 µs | 0.080 % |
| 27 Sep – 14 Oct | 791 | 87.3 µs | 259.9 µs | 415.0 µs | 559.6 µs | 0.013 % |
Until 26 September a system thread woke every 1 ms, the same period as the probe, and that favoured the probe. Since then it sleeps when there is no work and no longer perturbs the system. An A/B on 15 October with the same module confirms it: with the 1 ms pulse the probe reads p99 = 159 µs, without it 280 µs. We do not perturb the system to improve a measurement, so the second interval is the one that stands; missed cycles fell from 0.080 % to 0.013 % across the same step. These figures describe the probe, not a workload.
E3Saturation of the fast domain
Workload. A real-time graphics pipeline whose resident set exceeds the fast domain, run as a user plays it: seven runs on 23–24 Oct 2026, 425,860 frames, 133 minutes. It is chosen because it drives to the boundary (maximum 0.9984) while the accelerator runs near full duty: the regime in which (1.1) predicts a discontinuity.
Observable. The frame period , recorded per frame by an in-process overlay, in units of the presentation period s. Occupancy, accelerator duty and host load are recorded on the same frame and enter only as ratios. Arm. Single arm, BACQM active: this campaign tests the shape of near , not a difference against CONTROL (that is E1). Kernel log over the seven runs: no panic, no out-of-memory action, no guard termination.
Frame period per occupancy stratum
τ/T₀ · saturation_strata.csvTable view
| Stratum of s | frames | q50 | q95 | q99 | q99.9 | τ > 3 T₀ | host load |
|---|
The median does not move: 1.01–1.04 in every stratum. For the p99 stays at or below 4.85 , and the top stratum has a lighter tail (p99 3.55) than the one beneath it (4.84). The only heavy tail is at , where the frames are asset loading and the fast domain is nearly empty. This is Observation 4 of the formal note.
One run, 15-second windows
saturation_windows_15s.csvTable view
| t (min) | frames | s | duty | host | q50 / T₀ | q99 / T₀ |
|---|
The shaded band is . When occupancy and duty rise together the median frame period rises with the duty (Observation 5: 1.32 on the 31,222 frames with and duty ≥ 0.90), while the host load stays at 0.20: the pipeline is bound by the accelerator's compute, not by the boundary of its memory. Within single 15-second windows the p99 can leave the scale (▲): these are the rare long frames that the p99.9 column counts, finite and isolated, never a sustained stall.
| Run (local start) | frames | minutes | max s | q50 / T₀ | q99 / T₀ | q99.9 / T₀ | host | duty ≥ 0.9 |
|---|
E4The transport ledger
Cumulative counters of the transport operator of §4, read at the kernel interface on 24 Oct 2026. Counts are in granules, the unit the operator reads from the running system; requests alternate direction.
| Direction | requested | completed | rejected |
|---|---|---|---|
| 𝒱 → ℛ (evacuation) | 630 | 630 | 0 |
| ℛ → 𝒱 (admission) | 630 | 626 | 4 |
| Total | 1,260 | 1,256 | 4 |
Requested mass equals completed plus rejected mass to the byte; the net transport granules is exactly the rejected set, as Proposition 3 requires, and every rejection was an admission into a fast domain at its boundary. Completion 0.9968, imbalance 0.32 % of the transported mass.
E5Extreme-entropy asymptotic allocation
Workload. An unconstrained symbolic proof-resolution pipeline executing deep recursive dependency search over an extensive axiomatic corpus, operating continuously for >60 minutes (2 Nov 2026). The active resident set exceeds 20 % of total host memory (>6.5 GiB in a single task tree), accompanied by concurrent asynchronous dirty-page writeback workers.
Observable. Run-queue scheduling delay () sampled at 60-second intervals via non-invasive eBPF scheduler probes (sched_ext with the nava operator manifold), memory pressure stall duration (), and directional page transport flux ().
Sustained symbolic saturation: run-queue latency and paging flow
60 s sampling · kernel telemetry| Epoch (UTC) | Load 1m | p50 | p90 | p99 | p99.9 | pswpout (pages) | pswpin (pages) | PSI mem | Attractor Zone |
|---|---|---|---|---|---|---|---|---|---|
| 03:48:45 (Basal) | 0.25 | 4 µs | 18 µs | 42 µs | 2,621 µs | 0 | 70 | 0.00 ms | POTENCIA_PLENA |
| 03:58:45 (Allocation shock) | 6.08 | 2 µs | 17 µs | 85 µs | 421 µs | 41,772 | 998 | 320.07 ms | POTENCIA_PLENA |
| 04:01:45 (Entropic evacuation) | 2.17 | 1 µs | 25 µs | 147 µs | 2,003 µs | 124,137 | 6,417 | 704.27 ms | EIGENSTATE |
| 04:03:45 (Memory peak) | 7.31 | 3 µs | 78 µs | 539 µs | 1,694 µs | 5,363 | 733 | 1,069.68 ms | EIGENSTATE |
| 04:10:45 (Compute peak) | 9.25 | 12 µs | 920 µs | 2,694 µs | 4,011 µs | 11 | 1,620 | 477.06 ms | EIGENSTATE |
| 04:20:45 (Bifurcation settling) | 5.54 | 21 µs | 1,402 µs | 4,608 µs | 7,168 µs | 320 | 748 | 495.86 ms | EIGENSTATE |
| 04:24:45 (Asymptotic quiescence) | 4.50 | 4 µs | 720 µs | 4,018 µs | 7,680 µs | 0 | 5,773 | 0.06 ms | CONVERGIENDO |
| 04:36:45 (Equilibrium) | 5.10 | 4 µs | 812 µs | 7,680 µs | 10,240 µs | 0 | 536 | 0.02 ms | EIGENSTATE |
| 04:46:46 (Stabilized) | 1.60 | 4 µs | 20 µs | 7,680 µs | 13,312 µs | 0 | 294 | 0.03 ms | POTENCIA_PLENA |
| 04:52:46 (Steady state) | 2.33 | 2 µs | 15 µs | 521 µs | 9,216 µs | 0 | 7,445 | 0.30 ms | CONVERGIENDO |
The 7-collector bundle partition. Paged allocations are uniformly distributed across equal-precedence compressed collectors (, cyclic symmetry ):
| Collector | Bound | Raw Volume | Compressed Footprint | Compression Ratio | Precedence |
|---|---|---|---|---|---|
| ℛ₀ | 4.0 GiB | 194.8 MiB | 72.2 MiB | 2.70 : 1 | 100 |
| ℛ₁ | 4.0 GiB | 192.0 MiB | 54.0 MiB | 3.55 : 1 | 100 |
| ℛ₂ | 4.0 GiB | 183.7 MiB | 52.8 MiB | 3.48 : 1 | 100 |
| ℛ₃ | 4.0 GiB | 179.7 MiB | 68.3 MiB | 2.63 : 1 | 100 |
| ℛ₄ | 4.0 GiB | 190.0 MiB | 69.7 MiB | 2.72 : 1 | 100 |
| ℛ₅ | 4.0 GiB | 192.4 MiB | 70.7 MiB | 2.72 : 1 | 100 |
| ℛ₆ | 4.0 GiB | 194.1 MiB | 73.0 MiB | 2.66 : 1 | 100 |
| Aggregate | 28.0 GiB | 1,326.7 MiB | 460.7 MiB | 2.88 : 1 | — |
1. Microsecond median under load 9.25: Conventional schedulers experience priority inversion and tail explosion under memory-induced writeback stalls. Here, the scheduler's median dispatch delay remains locked between 1 µs and 12 µs throughout the entire session.
2. Asymptotic zero-evacuation: Following an initial burst of pages evacuated into the 7-way bundle, outward swap drops to strictly zero () for over 30 minutes, preventing any swap-thrashing stall.
3. Zero-OOM safety: The invariant memory guard recorded zero liquidations (, ), and the uncertainty bound remained certified on every tick.
E6Substrate
The implementation lives in kernel space and names no device, no vendor and no size: every bound it uses is read from the running system. One source, two instruction-set architectures.
| Architecture | State |
|---|---|
| x86-64 | continuous operation; every measurement on this page |
| ARM64 | modules loaded and verified, 21 Sep 2026 |
| Multi-node fabric | pilot stage: the law is the same, the measurement is next |
Kernel source is private. Methodology, data and the mathematics are open. For a pilot, open an issue.