Linked by Peter Gerdes on Mon 10th Jan 2005 17:35 UTC
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
Linked by Thom Holwerda on 06/14/13 11:39 UTC
Linked by Thom Holwerda on 06/14/13 11:32 UTC
Linked by Thom Holwerda on 06/13/13 19:39 UTC
Linked by Thom Holwerda on 06/13/13 14:45 UTC
Linked by Thom Holwerda on 06/13/13 11:43 UTC
More News »
Sponsored Links



There is no way JIT can ever be faster, because whatever you do it's all opcodes in the end - and with the JIT you have the overhead of doing the compiling at runtime. It's revealing that I have yet to see a major java app without a splash screen, and ime performance when running is also far lower, at least in a GUI. Anyway, while it's true that JIT code running on an Athlon can be faster than arch=i386 compiled code on the same machine, natively compiled code for your machine will always be faster than JIT.