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 42302
To read all comments associated with this story, please click here.
RE: Unfair comparison
by Simba on Sun 9th Oct 2005 21:00 UTC in reply to "Unfair comparison"
Simba
Member since:
2005-10-08

"Most c++ objects are either allocated on the stack or copy constructed into a container. In other words, near zero calls to malloc/free."

Um... What do you think happens when you use the "new" operator in C++? Ahd where do you think that container memory comes from?

Reply Parent Score: 1