JSThreadsAndGC: Difference between revisions

JSThreadsAndGC (view source)

129 bytes added , 23 April 2010

638

edits

@@ Line 23: / Line 23: @@
 The next big step after that is generational mostly-copying GC. We want that too but it's another similar amount of work, I think.
-Separately, it seems like a good idea to work on local optimizations. For example, Gregor noticed that we spend a lot of time in object finalization. Part of that time is to deal with custom finalizers, which most objects don't have. It might be faster if we allocated objects with custom finalizers in a separate GC arena. And Igor has suggested sweeping the non-custom objects in the background thread.
+There will also be opportunities to optimize the GC independent of these major overhauls. I don't know what they all are. We'll find them as the benchmark suite gets finished and we start measuring. For example, Gregor noticed that we spend a lot of time in object finalization. Part of that time is to deal with custom finalizers, which most objects don't have. It might be faster if we allocated objects with custom finalizers in a separate GC arena. And Igor has suggested sweeping the non-custom objects in the background thread.
 {| width="80%" cellspacing="1" cellpadding="6" border="0"