Open
Bug 1753783
Opened 4 years ago
Updated 8 months ago
Consider relying on interruptions for normal Gecko GC slice budgets
Categories
(Core :: JavaScript: GC, enhancement, P3)
Core
JavaScript: GC
Tracking
()
NEW
People
(Reporter: sfink, Unassigned)
References
(Blocks 1 open bug)
Details
Right now, GC slice budgets are usually determined by how much idle time we expect to have. But we also interrupt the GC if something happens that requires a response. If we could ensure that anything important does indeed request an interrupt, then we could more safely overestimate the available idle time. This would complete GCs faster, possibly increasing throughput by reducing cache cluttering, and perhaps go quiescent sooner (reducing power usage).
The main example of a reason to interrupt would be that it's time to prep for the next frame. We would need a timer to fire (or similar) so that we could set the atomic interrupt flag.
Updated•3 years ago
|
Severity: -- → S3
Priority: -- → P3
Updated•8 months ago
|
Blocks: GC.performance
Severity: S3 → N/A
You need to log in
before you can comment on or make changes to this bug.
Description
•