Edition of Wednesday 11 November 2026

Why a Java pod gets OOMKilled in Kubernetes with a half-empty heap

Comments on “Why a Java pod gets OOMKilled in Kubernetes with a half-empty heap”

3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked

A Java pod can be OOMKilled while its heap is only half full, because the container memory limit also has to cover metaspace, thread stacks, the code cache and direct buffers.

Read the original at zhukovskyi.space. 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. 23 of 143 with a score of 0.62. The panel rated it highest on practical relevance (0.86) and new information (0.81), lowest on significance (0.46). Placed No. 23, No. 64 by score alone: the placement terms moved other stories past it.

AI judgeJudge 2claude-haiku-5-5
Practical, technically specific guide on JVM memory in Kubernetes with a reproduction and a tool; partly promotional for jvm-fit, and claims are backed by a self-run test rather than primary data.
AI judgeJudge 3gpt-5.6-luna
A practical Kubernetes/JVM failure analysis with reproductions, concrete sizing guidance, and a validation tool. It is useful and reasonably supported, though the evidence is limited to short tests and some claims are broad.

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.62total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.46
  • Reader interest0.75
  • Audience breadth0.57
  • Practical relevance0.86
  • Substantiated0.75
  • Technical depth0.81
  • New information0.81
  • Counts against: Promotional0.22
  • Counts against: Overclaim0.23

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.550.350.480.460.20+0.24+0.110
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.740.700.820.750.12+0.26+0.196
Audience breadthHow many people who build technology does it concern?0.570.600.550.570.05+0.13+0.075
Practical relevanceHow useful is it to someone who builds software or tech products?0.960.800.820.860.16+0.22+0.189
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.880.600.780.750.28+0.05+0.038
Technical depthHow technically substantive is it?0.990.750.680.810.31+0.05+0.040
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.850.600.990.810.39+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.130.350.180.220.22−0.19−0.042
OverclaimDo the headline or conclusions claim more than the body supports?0.170.300.220.230.13−0.11−0.025
Sum of contributions+0.621
Claim-check penalty0.000
Total, as published0.621

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

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 11 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 “Why a Java pod gets OOMKilled in Kubernetes with a half-empty heap”

More on Rubric

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