> Doing Google searches on Java vs C++ performance I found some Wikipedia > etc pages, that I don't trust much. There were a few subjective > sounding statements in there, and some comments talked about the new JIT > that might speed Java up. The only comments I almost trust were Java > probably does new/delete faster than C++ but tends to consume more > memory, and Java JIT might get code to same raw execution speed to same > as C++ (but 4 times slower is not unexpected).
There's a reason why some core parts of a system is done in a non- managed language like C/C++, i.e. even Android ships with an NDK for doing the heavy lifting. No matter how good a JIT can be, there's just overhead associated - especially with the heavy method-based JIT used by HotSpot. In essence we trade in responsiveness, predictability and memory with [eventual] speed. I would imaging that missing value-types from the JVM’s core typesystem could also be a problem, regardless of how careful the developer tries to avoid boxing. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
