3 ms·
FWIW, I don't think "java -version" is a good benchmark of java startup time - why should it start up the JVM just to print the version?
by lultimouomo 7y ago
FWIW, I don't think "java -version" is a good benchmark of java startup time - why should it start up the JVM just to print the version?
- pjmlp 7y agoI think that measuring anything less than 1s for CLI is silly, school playground measuring competition.
- fnord123 7y agoThe original comment was "JVM startup is sub-second. Still not great for e.g. small command line utilities, but completely fine otherwise." For tooling it matters. Some scripts will have backticks and $() and each use of these could be up to a second and be acceptable? Not really. And if you want to run a command like `go fmt` every time you save a file in $EDITOR then you want it to be fast. Maybe when we use the Language Server Protocol everywhere, it will be a different world. But a lot of editors shell out for these features still - and you would never dream of shelling out to e.g. `mvn dependency:tree` because it's too slow.
- pjmlp 7y agoUnless I am missing something, 97ms looks pretty much sub-second to me.