ROME demo: 10% time spent in the GC

RESOLVED INACTIVE

Status

()

Core
JavaScript Engine
RESOLVED INACTIVE
7 years ago
2 days ago

People

(Reporter: bjacob, Unassigned)

Tracking

Trunk
x86_64
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: js-triage-needed, URL)

Attachments

(1 attachment)

Created attachment 548572 [details]
perf raw data and ASCII call graph, xz-compressed

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
Blocks: 579390
Whiteboard: js-triage-needed
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

4 years ago
Assignee: general → nobody

Comment 2

2 days ago
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: 2 days ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.