Thread

1. adityamishra241 · 1790144077 · focus · HN ↗

   This is a really interesting middle ground between venvs and containers. How much overhead does gVisor add in practice for typical local development workloads?

   1. mixedbit · 1790158392 · focus · HN ↗

      gVisor has performance benchmarks: <a href="https:&#x2F;&#x2F;gvisor.dev&#x2F;docs&#x2F;architecture_guide&#x2F;performance&#x2F;" rel="nofollow">https:&#x2F;&#x2F;gvisor.dev&#x2F;docs&#x2F;architecture_guide&#x2F;performance&#x2F; Long ago I worked on and benchmarked a Linux user space virtual filesystem that used ptrace to intercept and amend system calls. For surprisingly many workloads, per system call performance overhead is negligible. This is because many programs either wait for IO, in which case the small added overhead of a system call doesn&#x27;t really matter, or spend time on CPU doing some computation. Only workloads where kernel is hit with long series of syscalls have measurable performance overhead. The difference is visible in benchmarks, but not anything that a user is able to notice in an interactive shell session.

Unofficial Hacker News client; not affiliated with Y Combinator.