Linked by Thom Holwerda on Sat 8th Oct 2005 18:40 UTC, submitted by anonymous
Java Programmers agonize over whether to allocate on the stack or on the heap. Some people think garbage collection will never be as efficient as direct memory management, and others feel it is easier to clean up a mess in one big batch than to pick up individual pieces of dust throughout the day. This article pokes some holes in the oft-repeated performance myth of slow allocation in JVMs.
Permalink for comment 42314
To read all comments associated with this story, please click here.
RE: Java *is* (relatively) slow!
by Simba on Sun 9th Oct 2005 21:24 UTC in reply to "Java *is* (relatively) slow!"
Member since:

Yeah, as others have pointed out, this link is worthless. The benchmarks are not even remotely accurate.

More controlled benchmarks have conclusively shown that in some cases, Java can outperform C++ because of the runtime optimization. As I said in another reply, Java can perform dynamic optimizations on code that C++ cannot even dream about since it is limited to only static optimizations at compile time.

Reply Parent Score: 1