Closed
Bug 1262321
Opened 9 years ago
Closed 2 years ago
Poor GC throughput in long-running session persistence task
Categories
(Core :: JavaScript: GC, defect)
Core
JavaScript: GC
Tracking
()
RESOLVED
FIXED
People
(Reporter: bugzilla.mozilla.org, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: perf)
Attachments
(3 files)
This is a followup to bug 1260475. I have captured GC logs over the uptime of several hours and looked at a few long jank periods with the profiler. It turns out that most of it is caused by session persistence (bug 912717) and the sessionmanager addon (filed a bug on their tracker).
Nevertheless both of those root causes *also* cause a massive amount of GC as knock-on effect.
Attached the compressed GC log.
The screenshot of the profiler shows a time span where the addon creates a session backup. This takes about 30 of wall time.
Based on the matched method name it seems that it actually spends its majority of time in GC. In other words, poor collector performance is responsible for the majority of the jank.
The inverse call graph for a similar event shows drainMarkStack/processMarkStack as the top item.
So I guess bug 638660 would be the lowest-hanging fruit here in terms of walltime throughput, although not in CPU cycles throughput.
Updated•9 years ago
|
Updated•4 years ago
|
Blocks: GC.performance
Updated•3 years ago
|
Severity: normal → S3
I'm no longer experiencing this issue.
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•