Closed
Bug 674343
Opened 13 years ago
Closed 5 months ago
ROME demo: 10% time spent in the GC
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: bjacob, Unassigned)
References
()
Details
(Whiteboard: js-triage-needed)
Attachments
(1 file)
|
476.43 KB,
application/x-xz
|
Details |
Running Google's ROME demo, perf says that we spend roughly 10% time in the GC. Maybe that's normal, I don't know.
The attached file is a xz-compressed archive containing the raw Perf data + ascii call graph attached.
It still runs decently fast, but uses 2G of RAM. An about:memory capture of the same run is here: attachment 548567 [details]
See also: bug 657115
|
||
Updated•13 years ago
|
Whiteboard: js-triage-needed
|
||
Comment 1•13 years ago
|
||
The ROME demo does a lot of empty-chunk GCs, and I didn't see it do a single compartmental GC, which could make it spend more time than it really needs to.
Version: unspecified → Trunk
|
Assignee | |
Updated•10 years ago
|
Assignee: general → nobody
|
||
Updated•2 years ago
|
Severity: normal → S3
|
||
Updated•5 months ago
|
Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•