CycleCollector/CCStatus-2007-05-11: Difference between revisions
Jump to navigation
Jump to search
| Line 22: | Line 22: | ||
* Two patches dbaron's review queue. | * Two patches dbaron's review queue. | ||
* After the two patches, we need to have specific test cases and look for leaks. | |||
== Next steps on performance (pauses) == | == Next steps on performance (pauses) == | ||
Revision as of 18:50, 11 May 2007
« previous meeting | index | next meeting »
Agenda
- status of patches in progress
- performance requirements
- next steps on performance and on memory leaks
Status of Pending CC Code in Bugzilla
Last week's next steps: Wait for patches (first 4 of 5) to land, then test more:
- Jonas will write a test case to generate cycles via document. STATUS: Patch landed and there has been a significan improvement in performance. Now we're seeing a large majority of time spent in JS GC
Performance requirements
Criteria for Performance Satisfactory:
- Double the current GC time.
Next steps on leaks
- Two patches dbaron's review queue.
- After the two patches, we need to have specific test cases and look for leaks.