Closed
Bug 1008762
Opened 11 years ago
Closed 10 years ago
Rethink our GC scheduling heuristics in light of GGC
Categories
(Core :: JavaScript: GC, defect)
Core
JavaScript: GC
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: terrence, Assigned: terrence)
References
(Blocks 1 open bug)
Details
Now that we have GGC, some workloads that would have triggered high-frequency GC will now no longer do so. This got me thinking about a couple other potential pathological cases. Our first step here is to surface enough data and add enough telemetry that we can figure out if there are new pathological behaviors at all.
| Assignee | ||
Updated•11 years ago
|
Assignee: nobody → terrence
| Assignee | ||
Comment 1•10 years ago
|
||
I don't think there are; at least nothing too bad has popped up in the last year and a half. We lower the amount of garbage, but the distance from low to high frequency gc is not all that big.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•