Safe CPU, memory, and kernel measurements for Odin

Research for Establish safe CPU, memory, and kernel measurements, part of Find the way to Odin’s build-ready specification.

Accessed: 25 September 2026. Status: recommendations for later decisions, not a selected workload suite. No benchmarks, stress tests, privilege changes, or host configuration changes were performed.

Findings that shape the decision

Odin can reuse established workloads and Linux interfaces, but no single tool measures system usability, peak performance, and hardware health. Keep four outcomes distinct:

Performance measurement: completed work per second or elapsed time under a specified workload.
Responsiveness: foreground request or wakeup latency, including its tail, under a specified competing load.
Pressure observation: time lost to CPU, memory, or I/O contention during that interval.
Health finding: a detected verification failure or reported hardware error, with the observation's coverage.

This separation follows the tools' actual contracts: sysbench benchmarks operations; schbench measures artificial requests and scheduling delays; PSI measures stalls; memtester checks memory contents. Stress-ng explicitly says it was not intended as a precise benchmark suite. Successful stress completion establishes only that the chosen work completed without detected failures under those conditions. sysbench schbench PSI memtester stress-ng

Candidate comparison

Maintenance observations describe inspected releases or repository activity, not a guarantee of future support. GPL notices and third-party dependencies need checking again for the exact distributable artifacts. Perf is distributed in the Linux source tree, whose COPYING specifies GPL-2.0-only with the syscall exception and notes that other licenses may also apply; preserve the selected tool and dependency notices. Linux COPYING

Candidate	Useful measurement and limitations	Controls, output, portability, maintenance
sysbench CPU / memory	CPU events are a small prime-search workload, not a general application-performance model. The memory test defaults to a 1 KiB block; its `100G` default is cumulative transfer size, not RAM allocation. A default run therefore cannot stand for DRAM bandwidth.	Thread, event, duration, warmup and percentile controls; human-readable built-in reports require a pinned parser. Upstream advertises x86_64 and aarch64 packages. GPL-2.0-or-later. Latest published release inspected: 1.0.20, April 2020; repository push activity March 2025. Void still packages 1.0.20. README CPU source memory source release metadata Void
schbench	Reports synthetic request latency, wakeup latency, and requests/second. Closer to responsiveness than peak throughput. Its server-inspired matrix workload deliberately penalizes preemption using per-CPU locks; this is not a desktop interaction model.	Runtime, worker/message counts, work size, request rate, affinity and JSON percentiles. Source has x86 and aarch64 paths; Linux pthread/futex interfaces, no normal root requirement found. Musl behavior remains unverified. GPLv2. Inspected upstream commit `6300b8f`, June 2025. methodology source
stress-ng	Appropriate candidate for controlled background load and selected verification diagnostics. Bogo operations are unsuitable as Odin's cross-test score foundation.	Explicit byte/worker/time caps, verification, YAML and differentiated exit codes. Upstream documents musl builds and testing on ARM64/x86-64. GPL-2.0-or-later; release 0.22.01, September 2026. Void's recipe has explicit musl handling. README manual release Void
STREAM	Established sustainable memory-bandwidth kernels: Copy, Scale, Add, Triad. No memory-latency or comprehensive error-detection result. Each array must exceed cache requirements; a small cache-resident run is not a compliant STREAM result.	Portable C; multicore uses OpenMP and its runtime. Array size is a build parameter in reference 5.10. Text output and numerical validation. Reference source dates to 2013: stable method, not evidence of a modern portability test matrix. Custom license permits use/redistribution but imposes result-naming/run-rule conditions. source and license run rules
lmbench `lat_mem_rd`	Pointer-chain latency over sizes/strides exposes cache, memory and TLB behavior. Its manual acknowledges vulnerability to stride-sensitive prefetchers; do not present this as an architecture-independent “true RAM latency.”	Warmup, repetitions, bounded size, text pairs. GPLv2 COPYING inspected; Intel's repository is active but contains old documentation. Portability and selected-file licensing need validation before adoption; not a recommended mandatory dependency yet. manual README COPYING metadata
cyclictest / perf	Cyclictest measures timer wakeup latency; perf supplies diagnostic counters. Neither is a substitute for foreground application response.	Cyclictest offers duration, histogram and JSON; source is GPL-2.0-only, current rt-tests release 2.11. Its startup tests permission to enter SCHED_FIFO even when ordinary policy is selected. Perf depends on kernel/PMU access and can emit JSON. Treat both as optional diagnostic coverage. cyclictest privilege check rt-tests release perf
memtester	Online checking of allocated memory, not all installed RAM. Failures can involve memory, CPU, temperature or power; the result does not identify a replaceable DIMM by itself.	Byte size and finite iteration count; default iterations are infinite. Text plus exit-bit mask. Record actual allocation and locking, not only exit status. GPL-2.0-only. Version 4.7.1's December 2024 fix addresses stricter C23/GCC 15 compilation; Void recipe inspected still selects 4.6.0. manual source changelog Void
Memtest86+	Offline, bootable diagnostics reach almost all memory without the resident OS. They cannot run as an ordinary in-terminal stage.	GPLv2. Stable v8.10, May 2026, lists x86, x86-64 and LoongArch64. Current main additionally lists AArch64 with UEFI boot. This is a stable/development difference, not certified aarch64 coverage. stable README development README release
EDAC / rasdaemon	Hardware-error telemetry, complementary to active tests. Availability depends on hardware, firmware, drivers and exposed events.	Read EDAC counters where accessible; optionally consume an existing rasdaemon history. Rasdaemon monitors kernel trace events and has database backends; its repository shows September 2026 activity and GPLv2 metadata. Starting it is a separate privileged monitoring action, not necessary to read available counters. EDAC ABI rasdaemon metadata

Measuring usability under contention

Recommendation: evaluate paired idle and loaded foreground-request measurements as a first-class candidate. Run the same bounded foreground work alone, with a fixed CPU background load, and with separately controlled memory pressure. Preserve normal scheduling policy, work size, thread count, placement, requested arrival rate, actual throughput, sample count, and latency distribution. Report absolute latency and degradation relative to idle; a fast idle result can coexist with poor responsiveness under contention.

Existing tools can supply the observations. Schbench records both request and wakeup latency, supports a fixed request rate, and can coexist with an independently bounded stress-ng background worker. Sysbench's rate-limited engine is another candidate: its source adds measured queue time to event duration and reports queue length. These remain synthetic proxies for foreground work; neither measures keyboard-to-pixel delay, terminal rendering, browser interaction, or application launch by itself. Those need their own workload definitions. schbench methodology schbench source sysbench queue sysbench timer

Schbench needs qualification before selection. Its README says warmup defaults to five seconds, while the inspected source defaults to zero and bypasses its warmup reset in request-rate mode. It uses gettimeofday, so clock adjustments can contaminate timing. Set options explicitly, retain the revision, validate timing conditions, and decide whether its deliberate preemption penalty fits Odin's goal. Do not adapt work size independently on every system and then compare the resulting latency as equal work. source

Cyclictest is a useful separate scheduler diagnostic. Its default behavior can hold /dev/cpu_dma_latency at zero and suppress deep idle states; --default-system avoids that tuning. The source's unconditional real-time privilege check prevents assuming that an ordinary-policy configuration is universally unprivileged. Its timer latency, especially under SCHED_FIFO, is a different measurement from a normal foreground application's response. manual source privileges

Kernel telemetry and compatibility

PSI: Read system and, where available, workload-cgroup cpu, memory, and io pressure. some is time when at least some tasks are stalled; full is time when all non-idle tasks are stalled together. The cumulative total counter permits interval deltas; rolling 10/60/300-second averages can smear a short benchmark across adjacent phases. System-wide CPU full is undefined and exposed as zero for compatibility—zero there cannot mean perfect responsiveness. PSI exists in the inspected Linux 4.20 source, but requires CONFIG_PSI and may be disabled by default pending psi=1. Probe actual files and readability, not only kernel version. PSI 4.20 documentation Kconfig

Capacity and pressure: Record usable RAM, MemAvailable, swap capacity/usage, process or cgroup memory, major faults, and swap/reclaim activity where exposed. MemAvailable is an estimate of memory available without swapping, not an allocation guarantee. Swap occupancy alone does not establish current pressure. /proc/stat supplies CPU time and steal time, but kernel documentation explicitly warns that iowait is unreliable. Correlate these observations with latency and PSI; do not derive a definitive bottleneck from CPU utilization or a single counter. proc documentation

Cgroups: Observe effective CPU affinity/cpuset, CPU quota, memory/swap limits and relevant ancestors. Host RAM and online CPU counts may exceed what the benchmark is allowed to use. Cgroup v2 cpu.stat records throttling; memory.events separates high-limit reclaim, OOM conditions and kills. Parse by key: the kernel explicitly allows new memory.stat entries in the middle. These interfaces are independent of a particular init system, but writable delegation and enabled controllers are not guaranteed on Void, deb, rpm, containers, or user sessions. cgroup v2

Perf: Treat hardware counters as enrichment. CONFIG_PERF_EVENTS, CPU PMU support, virtualization, perf_event_paranoid, capabilities and distribution policy can limit access. Kernel documentation recommends CAP_PERFMON over broad CAP_SYS_ADMIN; Odin should describe missing access rather than lowering system security settings. Record event identity and time-running percentage when multiplexing occurs. PMU-specific cache and pipeline events are not universal normalized scores. Perf's manual also warns of overhead at short sampling intervals, particularly below 100 ms. security Kconfig perf stat

Architecture/libc: Proc/sysfs/cgroup interfaces offer the strongest common layer across x86_64/aarch64 and glibc/musl. Workload binaries still need distinct, verified artifacts and recorded toolchain flags. Upstream stress-ng explicitly documents musl; sysbench's advertised architectures and Void recipes are useful evidence, but none of the inspected material certifies Odin's whole four-way architecture/libc matrix. STREAM additionally needs a compatible OpenMP runtime; rt-tests has library dependencies. A package recipe proves availability intent, not successful operation. Missing checks should carry reasons such as unsupported, permission denied, unavailable dependency, or insufficient safe resources. stress-ng sysbench Void recipes STREAM rt-tests Makefile

Resource safety and cancellation

The following is a proposed execution contract, with exact caps left to the safety decision:

Calculate a conservative working budget from current MemAvailable, effective cgroup/ancestor headroom, expected tool/runtime overhead, and a retained reserve. Recheck while running. There is no sourced universal percentage that guarantees safety when other programs allocate concurrently.
Where delegated cgroup v2 control exists, put disposable workers in their own subtree and keep the supervisor outside that subtree. memory.high induces reclaim/throttling and is not a hard cap; memory.max bounds charged memory and can invoke OOM inside the cgroup. memory.swap.max separately controls swap. Use deliberate limits and record them because they change results. Caps reduce risk; they cannot guarantee that an unrelated system-wide shortage never kills a process. cgroup v2
Reserve intentional pressure for explicitly selected, isolated work. Without reliable containment or enough reserve, recommend pressure observation and small bounded workloads, and report unavailable active-pressure coverage. Allocation success alone is insufficient: memtester's own manual warns about overcommit, swapping and OOM affecting other programs. memtester
Never expose memtester's physical-address/device modes in the normal benchmark path. They overwrite the mapped region and can crash the system when it belongs to another process or the kernel. For ordinary allocations, verify locked bytes and completed patterns/iterations. Linux permits unprivileged locking up to RLIMIT_MEMLOCK; larger locking requires suitable privilege, commonly CAP_IPC_LOCK. The tool's “run as root” advice should not force the entire TUI to run as root. manual Linux mlock
Use finite work/time limits and a supervisor deadline. For stress-ng, enable only reviewed stressors, verification where supported, and no OOM respawn (--oomable). Its --oom-avoid is a heuristic with measurement overhead, not containment. In 0.22.01, --vm-bytes describes a total across VM workers; other stressors have different allocation semantics, so retain the exact version and options. stress-ng manual
Cancel the worker process group gracefully, then terminate remaining descendants after a defined grace period; use cgroup.kill when accessible. Preserve a cancelled/partial result. Stress-ng documents SIGINT cleanup, but its timeout can overrun during uninterruptible calls or cleanup. No userspace deadline guarantees immediate cancellation of an uninterruptible kernel task. manual cgroup kill

Repetition, kernel settings, and TUI overhead

Recommendation: record warmup separately, repeat bounded measurements, retain all repetitions and dispersion, and report a median only at a clearly defined level. STREAM's official report takes the best iteration after discarding the first; a median of repeated STREAM run results is a different statistic. Do not silently relabel its internal minimum as a median, combine raw milliseconds with MB/s, or replace an unavailable result with zero. Overall score normalization belongs to the scoring decision. STREAM source

Record kernel/build identity, visible preemption/scheduler settings, CPU topology and allowed CPUs, NUMA placement, THP policy, libc, workload/compiler version and flags, governor/driver, boost, power source and temperature observations. NUMA placement and THP policy affect what memory workload is actually measured. Kernel CPUFreq documentation explains that scaling_cur_freq can be a requested state rather than measured frequency, and boost depends on thermal/power conditions and package load. A governor name or falling frequency alone does not prove thermal throttling. Correlate sustained performance with available temperatures, thermal trip/cooling states, and power/frequency evidence; unavailable sensors remain unavailable. CPUFreq NUMA THP thermal interfaces

For “single core,” specify whether the worker is pinned and how the core is chosen on heterogeneous CPUs. For “multicore,” specify workers relative to allowed CPUs, SMT and quota; do not silently change those rules between systems. Preserve the machine's existing configuration for the baseline. Potential governor, scheduler, THP, affinity or kernel changes should be advice or separately labelled experiments, not automatic optimization before measuring.

The TUI competes for CPU time, memory bandwidth, cache and terminal I/O. Recommend throttled graph updates, buffered logs, no expensive animation during timed sections, and a quiet measurement mode that preserves cancellation. Avoid hiding this by reserving a core without recording it: that reduces tested capacity. Later validation should compare quiet versus normal rendering on the slowest supported machines and establish an overhead budget. This is a proposed qualification experiment, not evidence that a particular redraw rate is already safe. Lmbench explicitly warns about competing cache/CPU work; PSI's own Kconfig notes overhead can show up in synthetic scheduler stress tests. lmbench Kconfig

Memory errors, VM coverage, and remaining decisions

Online memtester cannot touch RAM occupied by the kernel or other processes. It may allocate less than requested and may continue unlocked; inspected 4.7.1 source can then still exit zero if its pattern checks succeed. Parse allocation/locking evidence alongside exit bits and report “no errors detected in the tested allocation,” with size, iterations and duration. A mismatch warrants investigation, not an automatic RAM-replacement diagnosis. manual source

EDAC counters reset at driver initialization or explicit reset; preserve counter baselines and seconds_since_reset without resetting them. Corrected errors merit attention, but uncorrected errors may cause a panic before a counter increments. DIMM labels can depend on board-specific userspace mapping. Therefore missing EDAC nodes, zero observed deltas, and an empty rasdaemon history cannot certify error-free RAM. Offer offline follow-up where supported; decide how development-only AArch64 Memtest86+ support should be presented. EDAC ABI EDAC model Memtest86+ stable development

VMs can validate packaging, libc/architecture execution, permissions, telemetry fallbacks, cgroup containment and result handling. Guest CPU/memory scores describe the guest allocation and host scheduling conditions; steal time is useful context. They do not certify the host's DIMMs, ECC pipeline, cooling, physical memory-channel bandwidth, or representative bare-metal scheduler tails. Rasdaemon's upstream QEMU tests intentionally inject virtual nonfatal events: useful for exercising decoding, not proving physical hardware health. proc rasdaemon CI description

Recommended next decision: shortlist sysbench for a narrow CPU baseline, STREAM for bandwidth, schbench for responsiveness qualification, selected stress-ng workers for bounded load, and memtester plus available EDAC/RAS for diagnostics. Keep perf/cyclictest optional; defer mandatory memory-latency scoring until a candidate is validated. Final selection remains open.

The human-facing decisions still needed are the foreground workload's meaning; fixed versus relative background load; inclusion of responsiveness in the median score; safe resource reserves and privileges; repetition/time allocation within the 10–20 minute standard run; treatment of heterogeneous cores and missing coverage; and whether offline/development-tool guidance belongs in the first release.

Evidence limits: no candidate was built or executed across the target matrix. Context7 resolved Linux kernel, sysbench, memtester and rt-tests documentation. Stress-ng, STREAM and schbench searches returned unrelated libraries, so no false library match was used; their owning sources were inspected directly. Memtester's upstream HTTPS site failed certificate validation; the report uses the original source/manpage/changelog preserved by Debian, cross-checked against the Void 4.6.0 source archive checksum, and identifies the version difference. Exact artifact compatibility, parser contracts, resource budgets, and score repeatability require later qualification.

25 KiB Raw Blame History Unescape Escape