News for hackers. Stuff that matters.
Re:Fast JVM launching without the hassle of persistent JVMs by pjmlp on Saturday November 17, 2012 @10:03AM (#4798202)
What about just using AOT compilation?
Re:Fast JVM launching without the hassle of persistent JVMs by gtrak on Saturday November 17, 2012 @10:27AM (#4798244)
JVM startup overhead, not clojure runtime overhead. That's still there.
Re:Fast JVM launching without the hassle of persistent JVMs by pjmlp on Saturday November 17, 2012 @10:44AM (#4798277)
What startup overhead?

I meant AOT to native code.

Re:Fast JVM launching without the hassle of persistent JVMs by MichaelGG on Saturday November 17, 2012 @04:37PM (#4799068)
AOT to Native code just removes the JIT time. Any overhead of actually running the Java runtime and running initialization code is still there.
Re:Fast JVM launching without the hassle of persistent JVMs by gtrak on Tuesday November 20, 2012 @05:43PM (#4811775)
AOT already means something to clojurists. It means removing the extra runtime compilation phase of .clj into classfiles. The JIT is what the JVM does, which still occurs just like before.
Re:Fast JVM launching without the hassle of persistent JVMs by pjmlp on Wednesday November 21, 2012 @07:58AM (#4814040)
Unless the bytecode gets translated to native code ahead of time (AOT).

Although OpenJDK/Oracle JVM don't offer this option, other vendors do.

Re:Fast JVM launching without the hassle of persistent JVMs by pjmlp on Sunday November 18, 2012 @01:12AM (#4800022)
What?!
Re:Fast JVM launching without the hassle of persistent JVMs by bickfordb on Saturday November 17, 2012 @12:36PM (#4798548)
Most of the Clojure app startup time (~1.2s on my machine) is the Clojure runtime, not the JVM (usually less than 100ms).