CycleCollector/CCStatus-2007-05-11: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(fix previous link) |
||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<small>[[CycleCollector/CCStatus-2007-05- | <small>[[CycleCollector/CCStatus-2007-05-04|« previous meeting]] | [[CycleCollector/Status_Meetings|index]] | [[CycleCollector/CCStatus-2007-05-18|next meeting »]]</small> | ||
== Agenda == | == Agenda == | ||
| Line 11: | Line 11: | ||
Last week's next steps: Wait for patches (first 4 of 5) to land, then test more: | 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. | * 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 | ||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=368774 Support cycle collection of refcounted non-xpcom objects (aka, the XBL patch)]: in dbaron's review queue. | |||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=377884 Switch nsXPConnect::Traverse to use tracing]: waiting for some feedback from Igor, and should be ready for review after that. | |||
* [https://bugzilla.mozilla.org/show_bug.cgi?id=379718 using trace API for reference counts]: probably want to wait with this until after bug 377884 lands. | |||
== Performance requirements == | == Performance requirements == | ||
Criteria for Performance Satisfactory: | |||
* Double the current GC time. | |||
== Next steps on leaks == | == 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. | |||
== Next steps on performance (pauses) == | == Next steps on performance (pauses) == | ||
Latest revision as of 18:51, 18 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
- Support cycle collection of refcounted non-xpcom objects (aka, the XBL patch): in dbaron's review queue.
- Switch nsXPConnect::Traverse to use tracing: waiting for some feedback from Igor, and should be ready for review after that.
- using trace API for reference counts: probably want to wait with this until after bug 377884 lands.
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.