News for hackers. Stuff that matters.
Re:Multi-tenant Java 8 VM in beta by 6ren on Thursday September 19, 2013 @07:07AM (#6410909)
Fantastic for sharing, though the startup time improvement is minor (e.g. I saw 17% improvement). BTW: that SO comment references a pdf that shows how to include your own classes, on pages 61-62 http://www.oracle.com/technetwork/jp/ondemand/java/20110519-... tools link: http://hg.openjdk.java.net/jdk6/jdk6/jdk/file/tip/make/tools...

IBM's multi-tenancy gives 3.3 speedup, for HelloWorld - worse for others (maybe if they combined it with CDS?)

BTW: The only way to get instant Java startup is not to startup - use an already running JVM, with the classes already loaded. It's fast. Just leave it in the background til you need it - it's effectively a server. Especially good to invoke javac this way, for lightening compiles (if like me you don't use an IDE).

Re:Multi-tenant Java 8 VM in beta by rektide on Thursday September 19, 2013 @03:28PM (#6413688)
If one needs to be launching only a fixed set of programs fast, perhaps give CRIU, checkpoint restore in userspace, a try? Give the program time to warm up and load, checkpoint it, then restore a copy: run an already copy, rather than repeat the startup afresh. Post on CRIU from the same day: https://plus.google.com/113218107235105855584/posts/CNkhcV43...
Re:Multi-tenant Java 8 VM in beta by greyboy on Thursday September 19, 2013 @08:01AM (#6411073)
Interesting about keeping a JVM running for compilation. I'm curious about doing just this for my day job but can't seem to find a good explanation. Do you have any resources to point me to?
Re:Multi-tenant Java 8 VM in beta by jared314 on Thursday September 19, 2013 @12:14PM (#6412547)
For a persistent JVM, take a look at Nailgun [1].

Additionally, the Drip project [2] uses a swapping strategy, by keeping an additional JVM spun up in the background. It was apparently built because the authors had trouble with persistent JVMs containing old dependencies.

[1] http://www.martiansoftware.com/nailgun/

[2] https://github.com/flatland/drip

Re:Multi-tenant Java 8 VM in beta by 6ren on Thursday September 19, 2013 @11:35AM (#6412242)
javac is itself written in java, so you can write a little program that does that in a loop, waiting for some trigger. I actually just had it in a shell, waiting for you to hit return, which also called my code after compilation.

An unexpected benefit (unexpected to me, anyway) was that not only do you avoid the startup penalty, but you also benefit from JIT compilation of javac itself - every time it compiles, it gets faster! IIRC it's fairly substantial the first 10 times, but still improving at 50.

Here's a working minimal starting point I just put together for you (check docs, google, stackoverflow etc):

  import javax.tools.*;
  import java.io.*;

  class Demo {
    public static void main(String args[]) throws IOException {
      JavaCompiler compiler = ToolProvider.getSystemJavaCompiler();
      int result = compiler.run(null, System.out, System.out, args);
    }
  }

 java Demo Foo.java     # compiles Foo.java
Here's a stackoverflow answer suggesting something similar http://stackoverflow.com/a/793913/50979

BTW: I called out to a bash script to work out which source files had changed, because it's easier than writing that bit in java (and this compiler doesn't do that for you - it just compiles the explicitly listed source files).

HTH - let me know if you need more info. I've been thinking of using Jnotify to watch for source files being written to, so it's 100% automatic - one issue is that I save quite often, and each will trigger a compile (I'm doing this with plain javac and inotify at the moment).