JIT vs AOT Compilation
jg21 writes "This article on "Penguin-Driven" JVMs takes a look the performance of Java GUI applications based on the JFC/Swing API, and contends that the JIT-powered JVMs can't match a JVM with an ahead-of-time compiler ported to the Linux/x86 platform. With AOT compilation, says the CTO who has written this piece, real-world Swing applications performed perceivably faster. One is left wondering, will we now see the 'microbenchmark war' carried into the Linux camp?"
They want their idea back.
Patrick Doyle
I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
Patrick Doyle
I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
When will the TLA madness end? Oh, the humanity! At least provide definitions, for those god-fearing folk who may be interested but not up-to-date.
JVM: Java Virtual Machine, the virtual environment that every Java bytecode program runs within, abstracting real hardware for the program in question.
GUI: Graphical User Interface
JFC: Java Foundation Classes - the basic classes that are provided to developers upon which, or rather, with which, to build their programs.
API: Application Programming Interface, a defined way for software to interface with other software (i.e. to make library calls)
JIT: Just-In-Time compilation, compiles the program when it is being launched, for the machine it is being launched on, in order to prevent poor performance by compiling every instruction whenever it needs to be done
AOT: Mentioned in the article text, it means Ahead of Time. For details, read the linked story.
CTO: Chief Technology Officer. Name given to an executive in charge of new or current technology.
Now that you know what is going on, RTFA.
--Dan