To the author: https://www.youtube.com/watch?v=OonDPGwAyfQ In other words, thank you for the content, but this could really use some proofreading.
wow, that video was amazing! forwarded to some writer/editor friends. thanks!
Command-line apps with Clojure and GraalVM: 300x better startup times
11–20 of 66 posts
Re: Command-line apps with Clojure and GraalVM: 300x better startup times
#12To the author: https://www.youtube.com/watch?v=OonDPGwAyfQ In other words, thank you for the content, but this could really use some proofreading.
BTW - CLI-matic uses your excellent Orchestra.
Re: Command-line apps with Clojure and GraalVM: 300x better startup times
#13Generally speaking, startup times for Java / JVM based apps should be worked on next by the teams behind it; in the container age, fast startup is a good thing. I know the JVM itself starts up fast enough, but then going with e.g. Spring on top of that just adds a minute of startup time - and I've no clue what it's doing, I wouldn't think loading config, registering services and opening up a servlet thingy would take…
Long JVM startup time is a big reason why I went with Elixir instead of Clojure when I decided to move off Ruby to do webdev. (Another reason was easily triggering nasty Java stacktraces.)
My Elixir test suites fire up instantly and finish in seconds (if that) and this fast-as-possible feedback loop is extremely important to stay productive, IMHO.
Re: Command-line apps with Clojure and GraalVM: 300x better startup times
#14Re: Command-line apps with Clojure and GraalVM: 300x better startup times
#15Generally speaking, startup times for Java / JVM based apps should be worked on next by the teams behind it; in the container age, fast startup is a good thing. I know the JVM itself starts up fast enough, but then going with e.g. Spring on top of that just adds a minute of startup time - and I've no clue what it's doing, I wouldn't think loading config, registering services and opening up a servlet thingy would take…
I've found cdi starts much faster than Spring these days! Glad to see it catching steam
Re: Command-line apps with Clojure and GraalVM: 300x better startup times
#16ah this is great. I need to look at switching to Graal.
Graal can be used as the JIT compiler got your JVM. It's also pretty easy to hack on. There a great presentation on YouTube by one of the project leads about that.
Re: Command-line apps with Clojure and GraalVM: 300x better startup times
#17"So you have no excuses not to build your CLI tools in Clojure now."
Except that the toy program is 25MB and takes multiple minutes to compile...
Re: Command-line apps with Clojure and GraalVM: 300x better startup times
#18Re: Command-line apps with Clojure and GraalVM: 300x better startup times
#19Generally speaking, startup times for Java / JVM based apps should be worked on next by the teams behind it; in the container age, fast startup is a good thing. I know the JVM itself starts up fast enough, but then going with e.g. Spring on top of that just adds a minute of startup time - and I've no clue what it's doing, I wouldn't think loading config, registering services and opening up a servlet thingy would take…
There was an interesting London Java Community meetup[1] this week covering this topic. Matthew Gilliard demonstrated Class Data Sharing[2] and Application Class Data Sharing[3] and its impact on JVM startup times.
My work proxy is making it a pain to find the presentation, I'll try again at home.
[1] - https://www.meetup.com/Londonjavacommunity/events/252118399/
[2] - https://docs.oracle.com/javase/8/docs/technotes/guides/vm/cl...
Re: Command-line apps with Clojure and GraalVM: 300x better startup times
#20Generally speaking, startup times for Java / JVM based apps should be worked on next by the teams behind it; in the container age, fast startup is a good thing. I know the JVM itself starts up fast enough, but then going with e.g. Spring on top of that just adds a minute of startup time - and I've no clue what it's doing, I wouldn't think loading config, registering services and opening up a servlet thingy would take…
Long JVM startup time is a big reason why I went with Elixir instead of Clojure when I decided to move off Ruby to do webdev. (Another reason was easily triggering nasty Java stacktraces.) My Elixir test suites fire up instantly and finish in seconds (if that) and this fast-as-possible feedback loop is extremely important to stay productive, IMHO.
The editor based REPL is how the Clojure folks stay productive (as opposed to running tests at the command line). Using a keyboard shortcut to eval any expression in your code is really great.
The stacktraces are still often terrible though =/