Closed
Bug 535577
Opened 15 years ago
Closed 6 years ago
Opportunistically run incremental GC in interframe intervals
Categories
(Tamarin Graveyard :: Garbage Collection (mmGC), defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
Q1 12 - Brannan
People
(Reporter: lhansen, Unassigned)
References
Details
(Whiteboard: PACMAN)
Running the GC when nothing else is going on, even if we can only run it for a very short time every time, will lead to quicker completion and lower memory use without impacting mutator times except by (a) stealing time that should have been used for something else and (b) causing churn in caches etc. Very-large-heap issues brought on by the new GC policy (eg WE #2511890) might especially benefit from this.
Reporter | ||
Updated•14 years ago
|
Priority: -- → P5
Target Milestone: --- → flash10.1
Reporter | ||
Updated•14 years ago
|
Assignee: lhansen → nobody
Reporter | ||
Updated•14 years ago
|
Status: ASSIGNED → NEW
Whiteboard: PACMAN
Comment 1•13 years ago
|
||
Profiling some Flex transition tests shows some very inconsistent frame rates even though we are not pegging the CPU. The transitions are 1/2 a second and when a gc pass happens in the middle, we get 10 FPS instead of 35 or so. Having a mechanism to ask the gc to collect during the idle time we have would be a very nice addition.
Reporter | ||
Comment 2•13 years ago
|
||
Another bug you want to be commenting on is bug #631515. All remarks there are most welcome, because I intend to start working on that very soon.
Reporter | ||
Updated•13 years ago
|
Priority: P5 → P3
Reporter | ||
Updated•13 years ago
|
Target Milestone: Q3 11 - Serrano → Q1 12 - Brannan
Comment 3•6 years ago
|
||
Tamarin isn't maintained anymore. WONTFIX remaining bugs.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•