Edition of Friday 20 November 2026

Five Eligible CPUs, a Four-CPU Quota: What Runtimes Report and What It Costs

Comments on “Five Eligible CPUs, a Four-CPU Quota: What Runtimes Report and What It Costs”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Octri's Emad Khair compares what runtimes report in a container with five eligible CPUs but a four-CPU quota: Python 3.13 and Go 1.23 say five, Node.js 22 and OpenJDK 21 say four. In a small Python test, five CPU-bound workers instead of four left batch time near 1.0 s but raised 95th-percentile job time from 50.4 to 70.9 ms, with throttling in nine of ten periods. The workload is narrow, but it supports setting worker counts explicitly. Go 1.25 now considers cgroup quotas in its default GOMAXPROCS.

Read the original at octri.dev. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 11 of 140 with a score of 0.69. The panel rated it highest on technical depth (0.88) and new information (0.82), lowest on significance (0.53). Placed No. 11, No. 17 by score alone: the placement terms moved other stories past it.

AI judgeJudge 2claude-haiku-5-5
A well-substantiated engineering write-up with a reproducible measurement comparing runtime CPU-count defaults under cgroup quotas; practical for container worker sizing, though niche in scope and somewhat long.
AI judgeJudge 3gpt-5.6-luna
A well-supported, technically detailed comparison of CPU-count and quota handling across major runtimes, with reproducible measurements and concrete deployment guidance. It is broadly useful for performance-sensitive services, though not a landmark development.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.69total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.53
  • Reader interest0.76
  • Audience breadth0.63
  • Practical relevance0.81
  • Substantiated0.81
  • Technical depth0.88
  • New information0.82
  • Counts against: Promotional0.03
  • Counts against: Overclaim0.17

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.580.400.620.530.22+0.24+0.128
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.690.700.880.760.19+0.26+0.197
Audience breadthHow many people who build technology does it concern?0.710.600.580.630.13+0.13+0.082
Practical relevanceHow useful is it to someone who builds software or tech products?0.890.700.860.810.18+0.22+0.179
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.840.700.900.810.20+0.05+0.041
Technical depthHow technically substantive is it?0.990.800.850.880.19+0.05+0.044
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.890.600.980.820.38+0.05+0.041
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.040.050.010.030.04−0.19−0.006
OverclaimDo the headline or conclusions claim more than the body supports?0.220.250.040.170.21−0.11−0.019
Sum of contributions+0.687
Claim-check penalty0.000
Total, as published0.687

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #11 on Rubric, 20 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-20/11/"><img src="https://rubric.hrih.si/badge/2026-11-20/11.svg" alt="Ranked #11 on Rubric, 20 Nov 2026" width="245" height="28"></a>

Claim check

Claim check: 4 matches source · 4 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. Matches sourceNumber

    A CPython issue proposes accounting for cgroup CPU quotas in os.process_cpu_count(); its reproducer shows a container limited to two CPU-equivalents reporting 20 eligible CPUs.

    The cited source says the same thing.

    The article says

    “its reproducer shows a container limited to two CPU-equivalents reporting 20 eligible CPUs”

    The source says

    “$ docker run -it --cpus=2 python:3.14-slim python -c "import os; print(os.process_cpu_count())" 20”

    Source cited by the article: github.com/python/cpython/issues/149452

  2. No source givenVersion

    Python 3.13's default thread pool upper bound is min(32, (os.process_cpu_count() or 1) + 4).

    The article gives no link or citation for it.

    The article says

    “Python 3.13 uses min(32, (os.process_cpu_count() or 1) + 4) as its default upper bound”

    The source says

    No source to compare with.

  3. Matches sourceVersion

    Node.js's os.availableParallelism() is the API intended to estimate an appropriate amount of parallelism and delegates to libuv, which can take Linux cgroup bandwidth limits into account.

    The cited source says the same thing.

    The article says

    “os.availableParallelism() is the API intended to estimate an appropriate amount of parallelism. It delegates to libuv, which can take Linux cgroup bandwidth limits into account”

    The source says

    “Returns an estimate of the default amount of parallelism a program should use. Always returns a value greater than zero. This function is a small wrapper about libuv's uv_available_parallelism”

    Source cited by the article: nodejs.org/api/os.html

  4. Matches sourceVersion

    Java's container support documentation describes -XX:ActiveProcessorCount as an explicit override of the processor count.

    The cited source says the same thing.

    The article says

    “Java's container support documentation also describes -XX:ActiveProcessorCount as an explicit override”

    The source says

    “Overrides the number of CPUs that the VM will use to calculate the size of thread pools it will use for various operations such as Garbage Collection and ForkJoinPool”

    Source cited by the article: docs.oracle.com/en/java/javase/21/docs/specs/man/java.html

  5. No source givenNumber

    In the author's test, going from four to five CPU-bound worker processes left batch time nearly unchanged (1.014 s vs 1.000 s) but raised 95th-percentile job execution time from 50.4 ms to 70.9 ms, about 41%.

    The article gives no link or citation for it.

    The article says

    “Adding the fifth process made almost no difference to total throughput. It did increase the measured 95th-percentile duration of an individual job by about 41%”

    The source says

    No source to compare with.

  6. No source givenNumber

    In the five-worker run the cgroup was throttled in nine of ten periods, versus none of ten with four workers.

    The article gives no link or citation for it.

    The article says

    “In the measured run, the container was throttled in nine of ten periods with five workers, versus none with four”

    The source says

    No source to compare with.

  7. Matches sourceVersion

    Go 1.25, released in August 2025, changed the default GOMAXPROCS on Linux to consider cgroup CPU bandwidth limits as well as available logical processors, and to update the default periodically.

    The cited source says the same thing.

    The article says

    “Go 1.25, released in August 2025, changed the default behavior of GOMAXPROCS on Linux”

    The source says

    “On Linux, the runtime considers the CPU bandwidth limit of the cgroup containing the process, if any. If the CPU bandwidth limit is lower than the number of logical CPUs…”

    Source cited by the article: go.dev/doc/go1.25

  8. No source givenGeneralization

    Having more simultaneous workers than the container's CPU quota allows creates more concurrent work without letting the container do more total work, which makes throttling relevant to latency-sensitive services.

    The article gives no link or citation for it.

    The article says

    “A pool can create more simultaneous work without making the container capable of executing more total work”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 1 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 20 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Five Eligible CPUs, a Four-CPU Quota: What Runtimes Report and What It Costs”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.