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 42286
To read all comments associated with this story, please click here.
RE: memory allocation...
by Simba on Sun 9th Oct 2005 20:18 UTC in reply to "memory allocation..."
Member since:

"Mind you, allocations come in a distant second to the grand piece of suck that is swing. Basically, if you want a fast GUI, do nothing in swing events, pass it onto another thread, it's a pain in the ass, but that's the only way."

How is this different from any other toolkit? If you perform long running operations on the same thread that GUI events are dispathed on, you are going to freeze the GUI until that operation returns. I use Gtk quite a bit too, and it has the exact same problem.

Reply Parent Score: 1