Javascript:SpiderMonkey:ProjectGenerationGarbageCollection: Difference between revisions

<p>Objective: Implement Generational Garbage collection in Spider Monkey. &lt;Some goal based off V8 performance delta&#160;% on Earley Boyer benchmark&gt;

</p><p>Accountable: Naveed

<p>Responsible: Terrence, Jon, and Steve, evilpie Ms2ger

</p><p>Generational GC - Bug 619558

<p>Steps

</p><p>JIT Integration with post barriers - 4 weeks, parallelized

<p>IonMonkey [Bug 831506] - 1 week (bhackett)

Baseline JIT [Bug 831507] - &lt;ask jandem/djvj for an estimate&gt;

</p><p>Generation Garbage Collection in the Shell

<p>Implement prototype algorithm (terrence) - 1 week

</p><p>Exactly Root the Browser [Bug 831379] - 10 weeks

<p>This is a potential milestone: we would turn on exact rooting for release FF at this point. We would not get a performance boost from this (necessarily), but it would lock in our work to this point.

</p><p>Performance Tuning - 4 weeks (This should probably start asap)

<p>Test against V8 Earley-Boyer benchmark.

Refactor code to avoid rooting on hot paths and keep rooter overhead acceptable -&#160;??? weeks (start early) (bhackett)

</p><p>Re-implement HashTable rekeying

<p>We undid this code because it was a perf regression and was still a bit buggy. (terrence) - 3 weeks

</p><p>Make the Post Barrier Verifier Green in the browser [Bug 764882]

<p>Investigate how long it will take to do generational barriers - 1 week

</p><p>We may need to rewrite the maps in xpconnect and the browser in terms of HashTable: this could be a bunch of work.  

<p>Make JS_IsAboutToBeFinalized indirect [Bug 765432] - 10 weeks

</p><p>OTHER

</p><p>Should we establish a new  benchmark specifically for GGC. (sfink votes yes)

<p>What would it measure? there are multiple goals, e.g. throughput/MMU/pause time

</p><p>Risks

<p>Team is responsible for many top crashers