Closed Bug 1367900 Opened 8 years ago Closed 8 years ago

Add information on GC trigger thresholds to profile JSON

Categories

(Core :: JavaScript: GC, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla56
Tracking Status
firefox56 --- fixed

People

(Reporter: sfink, Assigned: sfink)

Details

Attachments

(1 file, 1 obsolete file)

It would be nice to be able to correlate GC speeds to memory utilization.
Sorry, the naming isn't great. Suggestions welcome. Also, it would probably be a lot more interesting to capture the amount of free physical memory or something. But at least this will help in cases where we're repeatedly hitting an allocation trigger or something.
Attachment #8871452 - Flags: review?(jcoppeard)
Make it compile and add in malloc triggers.
Attachment #8871545 - Flags: review?(jcoppeard)
Attachment #8871452 - Attachment is obsolete: true
Attachment #8871452 - Flags: review?(jcoppeard)
Comment on attachment 8871545 [details] [diff] [review] Record the values and thresholds for GC triggers Review of attachment 8871545 [details] [diff] [review]: ----------------------------------------------------------------- Great, it will good to record this information. ::: js/src/jsgc.cpp @@ +3010,2 @@ > triggerZoneGC(zone, JS::gcreason::ALLOC_TRIGGER); > } else if (usedBytes >= igcThresholdBytes) { We should move the recordTrigger call into triggerZoneGC since this happens in a few places.
Attachment #8871545 - Flags: review?(jcoppeard) → review+
Pushed by sfink@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/6ddd2bf5d55e Record the values and thresholds for GC triggers, r=jonco
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla56
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: