Slashdot Mirror

← Back to Stories (view on slashdot.org)

JIT vs AOT Compilation

Posted by michael on from the tastes-great-less-filling dept.

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?"

3 of 57 comments (clear)

  1. 1998 called by p3d0 · · Score: 5, Funny

    They want their idea back.

    --
    Patrick Doyle
    I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
  2. Re:What's the point in Java bytecode anyway? by p3d0 · · Score: 5, Informative

    It is parse trees. It's stack-based, which is pretty much just a post-order traversal of expression trees. Think of bytecode as a file format for describing expression trees.

    --
    Patrick Doyle
    I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
  3. Re:Let me clarify by p3d0 · · Score: 5, Funny
    Yes, I have actually done this myself for x86 with my pet language's interpreter/compiler, so I'm not just talking out my arse.
    Oh, ok. For a moment there, I thought I was a professional JIT developer, but apparently I was mistaken.
    --
    Patrick Doyle
    I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....