2 ms·
Reading the repo, the benchmark includes the entire program execution from startup to reading the file. For the sub-second compiled languages, it's basically a
by Aurornis 11mo ago
Reading the repo, the benchmark includes the entire program execution from startup to reading the file.
For the sub-second compiled languages, it's basically a benchmark of startup times, not performance in the hot loop.
- igouy 11mo agoHow much difference would it make for these tiny programs? https://benchmarksgame-team.pages.debian.net/benchmarksgame/performance/nbodyinprocess.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
- nheer 11mo agoAuthor here. I just tested this with Zig by timing the segments inside the program: 1 billion iterations: - Startup + file read: 0.01ms - Computation: ~200ms - Overhead: 0.01% Even at 1 million iterations (0.24ms total), startup is only 4% overhead. At 1 billion it's essentially zero. The benchmark is definitely measuring the hot loop, not startup time.