The anatomy of a Tines gVisor sandbox
Comments on “The anatomy of a Tines gVisor sandbox”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Tines describes how its 3B automation product runs each step in a fresh gVisor sandbox that is deleted afterward, with images and volumes held outside it. Lazy image loading, a sentry page cache with read-ahead, and a credential-injecting proxy are the main pieces. By Tines's own benchmarks, cold lookups in a 900 MB database fell from 8.42 to 2.27 seconds, and a cache-export fix cut some builds from 51 to 7.9 seconds. The figures are unsourced and come from one company's tests.
Why it ranked
No. 15 of 142 with a score of 0.66. The panel rated it highest on technical depth (0.95) and new information (0.91), lowest on audience breadth (0.51). Placed No. 15, No. 36 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Deep, specific engineering write-up on gVisor sandbox internals, lazy image loading, and page caching with benchmarks; practitioner-useful but niche to sandbox and container infrastructure builders.
- AI judgeJudge 3gpt-5.6-luna
- A detailed engineering account of gVisor sandbox architecture, persistent storage, lazy image loading, caching, networking, cleanup, and measured performance improvements. It is highly technical and useful, though framed around the company’s platform.
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.66total under rubric v2.3
- Significance0.55
- Reader interest0.83
- Audience breadth0.51
- Practical relevance0.68
- Substantiated0.86
- Technical depth0.95
- New information0.91
- Counts against: Promotional0.13
- Counts against: Overclaim0.12
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.58 | 0.35 | 0.72 | 0.55 | 0.37 | +0.24 | +0.132 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.78 | 0.80 | 0.91 | 0.83 | 0.13 | +0.26 | +0.216 |
| Audience breadthHow many people who build technology does it concern? | 0.47 | 0.45 | 0.62 | 0.51 | 0.17 | +0.13 | +0.067 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.70 | 0.55 | 0.78 | 0.68 | 0.23 | +0.22 | +0.149 |
| 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.89 | 0.80 | 0.88 | 0.86 | 0.09 | +0.05 | +0.043 |
| Technical depthHow technically substantive is it? | 0.99 | 0.92 | 0.94 | 0.95 | 0.07 | +0.05 | +0.047 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.86 | 0.90 | 0.97 | 0.91 | 0.11 | +0.05 | +0.046 |
| 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.06 | 0.15 | 0.18 | 0.13 | 0.12 | −0.19 | −0.025 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.12 | 0.15 | 0.08 | 0.12 | 0.07 | −0.11 | −0.013 |
| Sum of contributions | +0.662 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.662 | ||||||
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.
<a href="https://rubric.hrih.si/editions/2026-11-18/15/"><img src="https://rubric.hrih.si/badge/2026-11-18/15.svg" alt="Ranked #15 on Rubric, 18 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 1 matches source · 6 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenNumber
Tines runs millions of steps a day across its workers.
The article gives no link or citation for it.
The article says “We run millions of steps a day across what we call "workers”
The source says No source to compare with.
No source givenBenchmark result
In Tines's file-I/O benchmark, 200 cold lookups in a 900 MB database went from 8.42 seconds to 2.27 seconds after the read-ahead and reclamation changes.
The article gives no link or citation for it.
The article says “200 cold lookups in a 900 MB database went from 8.42 seconds to 2.27 seconds”
The source says No source to compare with.
No source givenBenchmark result
A SQL scan went from 13.0 seconds to 3.13 seconds after the changes, while a single point read stayed at 37 ms.
The article gives no link or citation for it.
The article says “A SQL scan went from 13.0 seconds to 3.13 seconds, while a single point read stayed at 37 ms”
The source says No source to compare with.
No source givenNumber
After the cache-export fix, the third and fifth builds fell from 51 seconds each to 7.9 seconds each.
The article gives no link or citation for it.
The article says “the third and fifth builds fell from 51 seconds each to 7.9 seconds each”
The source says No source to compare with.
No source givenNumber
In one production trace, BuildKit found a cache hit in about a quarter of a second, then spent 23.5 seconds downloading and unpacking parent layers for a COPY that took 0.03 seconds.
The article gives no link or citation for it.
The article says “BuildKit found a cache hit in about a quarter of a second, then spent 23.5 seconds downloading and unpacking parent layers for a COPY that took 0.03 seconds”
The source says No source to compare with.
No source givenNumber
The earlier implementation copied a volume file before open returned, and one production database had grown to 933 MB, requiring a full copy before a single row lookup.
The article gives no link or citation for it.
The article says “one production database had grown to 933 MB, which meant copying all of it before SQLite could look up a single row”
The source says No source to compare with.
Couldn’t checkVersion
Tines contributed support for chunk-based files to gVisor's EROFS reader, and that work is now upstream.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “We also contributed support for chunk-based files to gVisor’s EROFS reader. That part is upstream now”
The source says No passage could be compared.
Source cited by the article: github.com/google/gvisor/pull/15527
Matches sourceDate
gVisor is moving to the CNCF, and Tines has committed to joining its maintainers alongside Modal and Ant Group.
The cited source says the same thing.
The article says “as gVisor moves to the CNCF, Tines has committed to joining its maintainers alongside Modal and Ant Group”
The source says “With this move, Ant Group, Modal, and Tines have committed to join gVisor's maintainers , with OpenAI, Tencent, and NVIDIA continuing their contributions”
Source cited by the article: cloud.google.com/blog/products/containers-kubernetes/open-infrastructure-for-autonomous-agents-comes-to-cncf
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 1 pts, not on front page
Recorded for context only, checked 18 Nov 2026, 05:47 UTC. It played no part in the ranking.