Open Bug 1351789 Opened 8 years ago Updated 8 months ago

Add Telemetry probes for measuring garbage volume per GC

Categories

(Core :: JavaScript: GC, enhancement, P3)

Product:
Core
Component:
JavaScript: GC
Version:
50 Branch
Type:
enhancement

Tracking

()

Project Flags:
Performance Impact low

People

(Reporter: djvj, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: perf)

We're currently trying to address the issue of doing too many GCs, and many of those GCs lasting too long. Looking to relax and be less aggressive on GCs requires good knowledge of the behaviour of our current GCs: 1. What is the type of GC. 2. What is the heap size when each GC runs. 3. What is the change in heap size between each GC run. 4. What is the "considered set" of each GC. 5. What is the amount of memory freed by each GC run. Which of these do we have telemetry for, and which do we not? How hard would it be to add these probes?
Blocks: 1351769
Whiteboard: [qf]
Whiteboard: [qf] → [qf:p3]
I agree with the aim but we need to agree the set of measurements which are going give us the most value in improving the GC.
Keywords: perf
Priority: -- → P3
Performance Impact: --- → P3
Whiteboard: [qf:p3]
Severity: normal → S3

Is this already being reported?

You need to log in before you can comment on or make changes to this bug.