3 ms·
One thing I am looking forward to in JDK 9 is the new API, called JVMCI, that lets you replace HotSpot's JIT compiler with one written in Java. Oracle Labs is w
by chrisseaton 10y ago
One thing I am looking forward to in JDK 9 is the new API, called JVMCI, that lets you replace HotSpot's JIT compiler with one written in Java. Oracle Labs is working on a compiler for this called Graal. We're using this to make languages other than Java running on the JVM, like JRuby, run faster by using the JIT compiler API directly.
(I work for Oracle)
- pacala 10y agoI've been vaguely following JPython's story, and the limit is less the Python language, and more the Python runtime environment and its reliance on C APIs written with the GIL assumption in mind. http://jyni.org http://jyni.org doesn't appear to be ready for prime time, though there is recent progress, https://github.com/Stewori/JyNI/issues/2 https://github.com/Stewori/JyNI/issues/2. Does JVMCI bring hope for JPython + JyNI ?
- chrisseaton 10y agoYes JVMCI can help there in a couple of areas. Part of Graal (the new compiler) is a new FFI that bypasses JNI and can represent native calls directly in the JIT. That should improve native call performance. There is also a C interpreter with JIT being built on top of Graal and JVMCI. In JRuby we're looking at interpreting C extensions rather than running them as native code. In some cases this is faster than the native code, because we can optimise the Ruby and the C code together.
- gravypod 10y agoDo you know the guy who did the talk about optimizing Ruby for the way Ruby devs use Ruby? They used an example if an image library clamp function which was a mess. Using sort to clamp a value. Whoever that guy is, I'd like to be able to say he did an amazing job. Good work on your groups.
- mike_hearn 10y agoThat talk was by Chris, who you are replying to.
- gravypod 10y agoWell shit I've got to say that he is amazing! Chris keep up the good work. I look forward in seeing where you take it from here.