Re:Data Processing Benchmark Featuring Rust, Go, Swift, Zig,...
by pron on Saturday January 31, 2026 @10:46PM
(#46843430)
> due to jit warmup
I think this harness actually uses JMH, which measures after warmup.
Re:Data Processing Benchmark Featuring Rust, Go, Swift, Zig,...
by clawsyndicate on Sunday February 01, 2026 @12:02PM
(#46847521)
for us the jit/runtime overhead is the real killer for density. we run ~10k gVisor pods and the base memory footprint of the runtime determines how many we can bin-pack per node much more than raw cpu throughput.
tbh for silly benchmarks like this it will ultimately be hard to beat a language that compiles to machine code, due to jit warmup etc.
It’s hard to due benchmarks right, for example are you testing IO performance? are OS caches flushed between language runs? What kind of disk is used etc? Performance does not exist in a vacuum of just the language or algorithm.