Open
Bug 1008333
(GC.performance)
Opened 11 years ago
Updated 1 year ago
[meta] GC tracking bug for performance issues
Categories
(Core :: JavaScript: GC, defect, P3)
Core
JavaScript: GC
Tracking
()
NEW
People
(Reporter: terrence, Unassigned)
References
(Depends on 36 open bugs, Blocks 1 open bug)
Details
(Keywords: meta, perf)
This is a tracking bug for GC projects related to improving benchmark performance. Anything related to object allocation, finalization, or meta-object-graph analysis that improves our octane score belongs here.
This bug is only for blocking things we care about: P1 bugs -- lower priority bugs should not block this bug. Projects listed here will also be tracked on the JS Product Backlog.
Anyone working on GC should be following this bug and working on something under it.
Reporter | ||
Updated•11 years ago
|
Depends on: SemispaceGC
Reporter | ||
Updated•10 years ago
|
Depends on: ConcurrentMarking
Reporter | ||
Updated•10 years ago
|
Depends on: ParallelSweeping
Reporter | ||
Updated•10 years ago
|
No longer depends on: ParallelSweeping
Updated•9 years ago
|
Updated•9 years ago
|
Reporter | ||
Updated•9 years ago
|
No longer depends on: ConcurrentMarking
Updated•8 years ago
|
Updated•3 years ago
|
Assignee: terrence.d.cole → nobody
Status: ASSIGNED → NEW
Comment 2•3 years ago
|
||
We can use this meta bug to block performance issues. Since we're trying to have all bugs block a meta bug, we should relax the criteria in the description and have this block all perf issues.
Summary: [meta] GC time efficiency for tracking P1 bugs → [meta] GC tracking bug for performance issues
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•