On 15/02/2011 03:54, Andrew Whitworth wrote:
Even with that improvement, the GC is *still* regularly identified as a major performance problem in Parrot. 30% later and it's still one of our biggest problems.
GC performance problems are often more a symptom than a cause. With the current calling conventions even simple function calls create two GCables and make seven separate memory allocations if I read the code correctly. When profiling code, a lot of that shows up somewhere in the GC subsystem. But that doesn't automatically mean that the GC is our biggest problem. Generational GC is great, without a doubt. But it mainly helps with long running programs that consume a lot of memory.
Nick _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
