Re:Benchmarking 20 programming languages on N-queens and mat...
by nithril on Wednesday January 03, 2024 @12:02PM
(#38856449)
From nothing to result rarely happens in real live. I hardly see someone to start/stop a program per unit task (like piping commands).
Re:Benchmarking 20 programming languages on N-queens and mat...
by jltsiren on Wednesday January 03, 2024 @01:04PM
(#38857345)
Code compilation is a common example. In many languages, when you do a clean build of a large project, you run a large number of short-lived processes.
With command line tools, the dominant design philosophy is that a program completes one task and exits. The tasks may be large or small, and the same tools are often expected to handle both.
It doesn't make sense to allow "warmup" time for them unless your expected application is a server which for most of the time will be running "warm" (and even then with scalable containers that assumption may not even be true in some cases). For servers, however, what matters is mostly how fast its HTTP library is and how good the async IO is... check Techempower benchmarks for that: https://www.techempower.com/benchmarks/#hw=ph&test=fortune&s...