Measured Comparisons: 9 Guides From November 8, 2026
This index covers the 9 measured guides published November 8, 2026 — 1 C++ and 8 sysadmin / command-line. The 30 guides from November 9–10 have their own index.
Written November 11, 2026 · Tested with GCC 13 · 3 min read
- What this page is
- C++ — 1 guide
- Sysadmin and command line — 8 guides
What this page is
An index of the 9 measured guides published on November 8, 2026. The 30 measured guides from November 9–10 are listed in the companion index.
C++ — 1 guide
- How Fast Does std::jthread Actually Stop? Measured Shutdown Latency — a std::jthread worker that polls its stop token every 100 ms takes a median 46 to 73 ms to stop after request_stop; the same worker waiting on a condition variable stops in about 0.10 ms. Measured on GCC 13 and Clang 18.
Sysadmin and command line — 8 guides
- cgroup v2 MemoryMax: What Actually Happens When a Process Hits the Limit, Measured — a process that crosses a 128 MiB MemoryMax cap dies in about 25 milliseconds, with memory.peak exactly at the cap and almost no pressure stall. The same allocator under a 96 MiB MemoryHigh throttle takes about 101 seconds per 16 MiB step instead of about 17 milliseconds, and never gets killed.
- GNU Parallel Is Slower Than Serial: xargs -P vs GNU Parallel vs Serial, Measured — GNU Parallel is slower than a serial loop at every job count on short jobs, and floors at about 0.61 seconds on the heavy arm while xargs keeps scaling to 11.90x. The fresh run says 6.03x for xargs over parallel at 32 jobs.
- Logrotate copytruncate vs create: Measured What Happens to a Live Writer — under create, 7,087 lines land in the rotated file and 0 in the new one. Under copytruncate, 50 lines vanish in a 56 ms window. Measured on logrotate 3.21.0.
- nginx Reload vs Restart: What Actually Happens to In-Flight Requests — a reload dropped zero requests in three loops of about 26,000 each, with the longest pause 0.040 seconds. A restart dropped about 4,000 connection attempts per loop and left a 0.22-second hole. A slow download finished through a reload and through a graceful quit, and was cut to 39.1 percent by a stop.
- Ninja vs GNU Make, Measured: the Clean Build Is a Wash — the No-Op Isn't — the clean build is a wash (Ninja 3.437 s vs Make 3.566 s); the no-op rebuild is 11 times faster under Ninja (0.014 s vs 0.154 s); both binaries are byte-identical.
- The Regex That Hangs: Catastrophic Backtracking, Measured Across Five Engines — Python re takes 16.5 seconds at n=28, grep -P errors out at its backtracking limit, and ripgrep, Rust regex, and grep -E answer in about 2 ms. One possessive character fixes it 811-fold.
- rsync's 2,729x Speedup Is 1% Slower on the Clock: Delta vs Whole-File, Measured in Wall-Clock — rsync reported 'speedup is 2,729.37' for a delta transfer that moved 32,768 literal bytes, and the clock said it took 35.00 seconds against 34.63 for the whole-file copy. The byte counter is not a clock.
- systemd Timers vs Cron: What Actually Happens When a Run Is Missed — a systemd timer stopped for 34 seconds fired exactly once when it came back, one run for four missed elapses, while cron fired zero times for a minute already past. A 10-second timer with AccuracySec=30s ran 2 of 8 elapses when the offset was 8.87 seconds.
Related guides on this site
Keep Exploring
Paste a [Service] section and get a plain-language verdict on every sandboxing setting it finds.
Paste sshd -G output and get a hardening verdict on the values your server actually runs.
Paste a server block and get WebSocket, TLS, HSTS, and proxy-header verdicts.
Paste a systemd timer expression and get the specific reason it fails, the normalized form, and the past-date traps the built-in check hides.
The full sysadmin hub \u2014 systemd, cgroups, file tools, and measured Linux comparisons.