realexweb

5 ms·

1.
by realexweb 23d ago
Image already pulled: 3.7 ms for the box, and a shell command adds nothing on top (3.73 vs 3.71 over 100 runs, alpine). Python is 15.6 ms in a python:3.12-slim box, but ~12 of that is CPython starting, which you pay on bare metal too. Cold
2.
by realexweb 23d ago
The meaning of un‑cached can vary. The two un‑cached answers are very different. I will give both. When the image has already been pulled the container takes 3.7 milliseconds. Adding a command does not add any time. I ran /bin/sh
3.
by realexweb 23d ago
smolvm is a microVM .kern is plain OS-level isolation
4.
by realexweb 23d ago
thanks.. let me know how it goes or if you hit any issues
5.
by realexweb 23d ago
Fair, and it's not CRI. The README's limits section says "Not a Kubernetes runtime. No CRI. Use containerd or CRI-O." I meant runtime in the docker/podman sense, pull and build and lifecycle in one binary, and you&#
6.
Show HN: Kern – container and resource runtime in a 1.5 MB binary, no daemon(github.com)
70 points by realexweb 23d ago|9 comments
7.
by realexweb 2mo ago
Genuine question rather than a criticism: what do the tools actually execute in? I spent last week asking people running local agents what their generated code runs inside, and the answer was consistently "nothing" - same filesyst
8.
by realexweb 2mo ago
I've been benchmarking bare CPython startup for something unrelated and get 7.5ms median for python3 -c 'pass' on this machine, 5.3 with -S. That floor is most of the cost for anything short-lived. Does compiling natively byp
9.
by realexweb 2mo ago
Nice size. I've been fighting the same fight in Rust and landed at 1.9 MB for a static-pie musl binary, which is about as far as I could push it without giving up features. Two things that cost me the most, curious if they hit you the
10.
by realexweb 2mo ago
link