Closed
Bug 1491385
Opened 6 years ago
Closed 6 years ago
Use the unique performance counter ids in about:performance
Categories
(Toolkit :: Performance Monitoring, enhancement)
Toolkit
Performance Monitoring
Tracking
()
RESOLVED
FIXED
mozilla64
Tracking | Status | |
---|---|---|
firefox64 | --- | fixed |
People
(Reporter: florian, Assigned: florian)
References
Details
Attachments
(1 file)
8.96 KB,
patch
|
Felipe
:
review+
|
Details | Diff | Splinter Review |
Bug 1477943 introduced counter ids per my request, as I wasn't able to differentiate workers or to take into account sub frames that were gone. Let's use them!
Assignee | ||
Comment 1•6 years ago
|
||
With this patch, the "dispatches in the last seconds" column is now filled for sub-items (subframes of different origins, or workers). And when a subitem disappears, we can now add the last known values of its counter to the parent item, so that the total of the parent item doesn't go down. This makes the sort order much more stable. I also fixed a bug in how the 'oldest' variable was assigned, which caused new CPU hungry tabs to take up to 10 seconds to bubble up (now they'll go up within ~2s). And I changed the unit from s to ms for values < 1s, to avoid showing 0.<something> numbers.
Attachment #9009194 -
Flags: review?(felipc)
Updated•6 years ago
|
Attachment #9009194 -
Flags: review?(felipc) → review+
Pushed by florian@queze.net: https://hg.mozilla.org/integration/mozilla-inbound/rev/c921cc00eea3 Use performance counter ids in about:performance to display information for subitems and have a more stable sorting, r=felipe.
Comment 3•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/c921cc00eea3
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox64:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
You need to log in
before you can comment on or make changes to this bug.
Description
•