The anatomy of a Tines gVisor sandbox
Comments
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Summary
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.