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 42079
To read all comments associated with this story, please click here.
RE[2]: Doesn't matter....
by Simba on Sun 9th Oct 2005 02:16 UTC in reply to "RE: Doesn't matter...."
Member since:

"Concur. While Gosling is orders of magnitude smarter than me, when I saw JBoss take longer to boot than the Lose2000 OS on which it ran (the app in question was rather minimal), something ~3 minutes, IIRC, I thought: wow, no need to shop for a turkey this Thanksgiving..."

Speed of startup on a Web application server is of little importance. Performance when it is running is what matters. And when it comes to performance of Web applications written in Java, typical algorithms benchmark 10 to 15 times faster in Java than in Perl. (Java compiles mathematical algorithms that are commonly used down to native code with Hotspot). So Java would seem to be a much better option for a complex Web app than Perl for example. And for obvious reasons, C / C++ are usually not good options for writing Web applications.

Reply Parent Score: 2