Closed
Bug 781945
Opened 13 years ago
Closed 13 years ago
Improve GC telemetry
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla17
People
(Reporter: billm, Assigned: billm)
Details
Attachments
(1 file)
8.08 KB,
patch
|
mccr8
:
review+
|
Details | Diff | Splinter Review |
This fixes the problem where GC_MS records the total time between the start and the end of the GC. I considered using a different histogram for this, but since the old one is totally useless, I think we should just replace it.
It also adds a max pause field, which is a little more useful than the GC_SLICE_MS histogram, which records the time of every slice, and so tends to be somewhat optimistic.
I also had it record the time for root marking and gray marking. I don't have a good idea of how long these phases are taking in the wild, so it would be good to get some data on this.
Attachment #651010 -
Flags: review?(continuation)
Comment 1•13 years ago
|
||
Comment on attachment 651010 [details] [diff] [review]
patch
Review of attachment 651010 [details] [diff] [review]:
-----------------------------------------------------------------
Nice!
::: toolkit/components/telemetry/TelemetryHistograms.h
@@ +56,4 @@
> HISTOGRAM(GC_MARK_MS, 1, 10000, 50, EXPONENTIAL, "Time spent running JS GC mark phase (ms)")
> HISTOGRAM(GC_SWEEP_MS, 1, 10000, 50, EXPONENTIAL, "Time spent running JS GC sweep phase (ms)")
> +HISTOGRAM(GC_MARK_ROOTS_MS, 1, 200, 50, LINEAR, "Time spent running JS GC mark phase (ms)")
> +HISTOGRAM(GC_MARK_GRAY_MS, 1, 200, 50, LINEAR, "Time spent running JS GC mark phase (ms)")
nit: The descriptions of MARK_GRAY needs to be fixed.
Attachment #651010 -
Flags: review?(continuation) → review+
Assignee | ||
Comment 2•13 years ago
|
||
Comment 3•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
You need to log in
before you can comment on or make changes to this bug.
Description
•