> > Funny you should ask. We are trying to get funding right now to work on > this problem. We are pretty sure we know where the dead bears are, we just > need to find the resources to build the sledges and haul them out. We know > that the slowdown is due to some large internal memory structures in the > compiler that need remodularization. Because of them, you need a lot of RAM > and to give Java plenty of heap, or you end up getting killed by paging or > GC overhead. >
Memory is cheap, so that's easy to fix with hardware.... what about taking advantage of multiple CPU cores? When researching this I discovered someone who was trying to take advantage of multi-core CPU's in the Flex Builder: http://stopcoding.wordpress.com/ -chris
