Open Bug 1518061 Opened 6 years ago Updated 2 years ago

Provide heap usage info to the gecko profiler's counters

Categories

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

enhancement

Tracking

()

People

(Reporter: pbone, Unassigned)

References

(Depends on 2 open bugs, Blocks 1 open bug)

Details

The gecko profiler currently has the size of the JS heap reported in each GCMajor event. Bug 1517409 will add more information to GCMajor markers. In this bug I want to add counters that are recorded with each profiling sample. + Allocated memory as a profiler counter. + Heap capacity as a profiler counter.
No longer depends on: 1517409
Depends on: 1519298
Priority: -- → P5

In Bug 1521924 Paul Bone said:

there's some bugs leading up to it

I'm looking at surfacing all the work for this, as I would like to help move this forward to get the front end landed in the profiler. Would you mind linking to or filing the bugs that lead up to this?

Flags: needinfo?(pbone)

(In reply to Greg Tatum [:gregtatum] from comment #2)

In Bug 1521924 Paul Bone said:

there's some bugs leading up to it

I'm looking at surfacing all the work for this, as I would like to help move this forward to get the front end landed in the profiler. Would you mind linking to or filing the bugs that lead up to this?

Bug 1505589 - Jesup is making it so that SpiderMonkey can access the counters.
Bug 1517409 - I added heap size information to GCMajor amrkers
https://github.com/devtools-html/perf.html/pull/1640
Bug 1519298 - I will add support for counting allocations in the JS heap.
this bug - Add the above size & usage data as counters.
Bug 1505624 - Since collection is incremental, it's unclear how much memory was freed vs how much was allocated during that
collection, this bug should seperate them.
Bug 1473213 - Similar data for the nursery.
Bug 1521995 - Add counters for the nursery.

Bug 1471438 - My JS GC profiling metabug

Note that in this bug I wasn't intending to sample nursery allocated/used.

Flags: needinfo?(pbone)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.