Matthew Rosewarne on 21 Nov 2007 04:13:36 -0000 |
On Tuesday 20 November 2007, Josh Goldstein wrote: > I agree it isn't, but I wasn't talking about bytecode. > Java has had a JIT compiler for years now, that generates machine code. > Check out these results: > http://shootout.alioth.debian.org/gp4/benchmark.php?test=allâ=all Unless > I'm misreading that chart, Java looks like it's doing better than a _lot_ > of other languages. Clearly, there needs to be machine code at some point. JIT is just the technique the Java VM uses to transform its bytecode into executable machine code. There aren't really any other good ways to do what Java does, but compiling bytecode at runtime carries with it a considerable overhead. The code the JIT compiler generates may be as good as an equivalent C compiler, but that generation still needs to happen, so more resources will be used overall. %!PS: Remember: "Lies, damn lies, and benchmarks." :> Attachment:
signature.asc ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|