3 ms·
Not to mention the frankly idiotic JVM startup time that becomes a nightmare if you are just trying to make a commandline tool. And no, don't bother mentioning
by jlgreco 14y ago
Not to mention the frankly idiotic JVM startup time that becomes a nightmare if you are just trying to make a commandline tool.
And no, don't bother mentioning nailgun or the like. Those cures are worse than the illness.
- igouy 14y agoWhen your commandline tool needs several seconds CPU to complete the task, JVM startup time is irrelevant. The benchmarks game measurements posted by voidlogic include JVM startup time and yet many of the Scala programs are faster than the corresponding Go programs, when the programs run for seconds. So a Go n-body program can be faster than a Scala n-body program at 0.33secs over a small workload, but then over a larger workload take 32.1secs compared to 23.5secs for the Scala program. http://benchmarksgame.alioth.debian.org/u64q/program.php?test=nbody&lang=go&id=1 http://benchmarksgame.alioth.debian.org/u64q/program.php?tes... http://benchmarksgame.alioth.debian.org/u64q/benchmark.php?test=nbody&lang=scala http://benchmarksgame.alioth.debian.org/u64q/benchmark.php?t...
- jlgreco 14y ago> When your commandline tool needs several seconds CPU to complete the task And mine do not. Furthermore, when you program is but one of many steps in a pipeline, but is not the bottleneck, startup time can have a very noticeable effect. I've heard a million reasons why JVM startup times do not matter. You are telling me nothing new.
- igouy 14y agoNow you are telling us -- it depends :-)