Closed Bug 1189799 Opened 9 years ago Closed 9 years ago

about:performance shows duplicate lines for each addon (1 entry per parent + 1 content process)

Categories

(Toolkit :: Performance Monitoring, defect)

42 Branch
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla44
Tracking Status
firefox42 --- affected
firefox44 --- fixed

People

(Reporter: vladan, Unassigned)

References

Details

Attachments

(3 files, 1 obsolete file)

An example...

Send Tab to Device currently performs well.less
    Full name: jid1-mdjmA7if6lo8lA@jetpack.
    Impact on framerate: 0/10.
    CPU usage: 0%.
    System usage: 0%.
    Blocking process calls: 0%.
    Measure start: 957 seconds ago.
    Process: 8516 (parent).

Send Tab to Device currently performs well.less
    Full name: jid1-mdjmA7if6lo8lA@jetpack.
    Impact on framerate: 0/10.
    CPU usage: 0%.
    System usage: 0%.
    Blocking process calls: 0%.
    Measure start: 957 seconds ago.
    Process: 8392 (child).

Send Tab to Device currently performs well.less
    Full name: jid1-mdjmA7if6lo8lA@jetpack.
    Impact on framerate: 0/10.
    CPU usage: 0%.
    System usage: 0%.
    Blocking process calls: 0%.
    Measure start: 957 seconds ago.
    Process: 7064 (child).

Send Tab to Device currently performs well.less
    Full name: jid1-mdjmA7if6lo8lA@jetpack.
    Impact on framerate: 0/10.
    CPU usage: 0%.
    System usage: 0%.
    Blocking process calls: 0%.
    Measure start: 957 seconds ago.
    Process: 4144 (child).
PerformanceStats could identify that the same addonId appears in different children, and sum the results. This may lead to CPU/System usage higher than 100%.
Actually, about:performance is probably better suited to grouping the add-ons for display.
Bug 1189799 - Make sure that about:performance displays each add-on only once (front-end);r=felipe
Attachment #8652387 - Flags: review?(felipc)
Bug 1189799 - Make sure that about:performance displays each add-on only once (back-end);r=felipe
Attachment #8652388 - Flags: review?(felipc)
I'm reviewing this and wrapping my head around the new data structure, but before continuing or trying to figure out I have a question that I think is easier to just ask you: I think there's still value in also seeing the values individually (per-process), specially to see the different performance impact of add-ons in the chrome and the content processes. So I guess what I wanted to ask is if this new structure will make it harder to do that or will that be ok? Not asking to build this visualization here in this bug but I think the UI in the future could allow you to opt between aggregate or per-process values
Flags: needinfo?(dteller)
Actually, I hope that it will make it easier to display the information. Of course, the only way to be sure is to actually write that code :)
Flags: needinfo?(dteller)
Comment on attachment 8652388 [details]
MozReview Request: Bug 1189799 - Make sure that about:performance displays each add-on only once (back-end);r=felipe

https://reviewboard.mozilla.org/r/17149/#review15859

::: toolkit/components/perfmonitoring/AddonWatcher.jsm
(Diff revision 1)
> -            // We are only interested in add-ons.

q: what was the other thing that are not add-ons that is now included here? Won't this affect the behavior of AddonWatcher unexpectedly?
Attachment #8652388 - Flags: review?(felipc) → review+
Comment on attachment 8652387 [details]
MozReview Request: Bug 1189799 - Make sure that about:performance displays each add-on only once (front-end);r=felipe

https://reviewboard.mozilla.org/r/17147/#review15861
Attachment #8652387 - Flags: review?(felipc) → review+
https://reviewboard.mozilla.org/r/17149/#review15859

> q: what was the other thing that are not add-ons that is now included here? Won't this affect the behavior of AddonWatcher unexpectedly?

Well, `snapshot.componentsData` contains add-ons and webpages (and, depending on options, built-in components). Prior to the patch, we iterated through all this list and skipped stuff that wasn't an add-on. With the patch, we iterate through `snapshot.addons`, which contains only the add-ons.
Bug 1200138 - AddonWatcher now uses groupId to subtract between two instances of an add-on;r=felipe
Comment on attachment 8652387 [details]
MozReview Request: Bug 1189799 - Make sure that about:performance displays each add-on only once (front-end);r=felipe

Bug 1189799 - Make sure that about:performance displays each add-on only once (front-end);r=felipe
Comment on attachment 8652388 [details]
MozReview Request: Bug 1189799 - Make sure that about:performance displays each add-on only once (back-end);r=felipe

Bug 1189799 - Make sure that about:performance displays each add-on only once (back-end);r=felipe
Bug 1189799 - Make sure that about:performance displays each add-on only once (more tests);r?felipe
Attachment #8655616 - Flags: review?(felipc)
Comment on attachment 8655616 [details]
MozReview Request: Bug 1189799 - Make sure that about:performance displays each add-on only once (more tests);r=felipe

https://reviewboard.mozilla.org/r/17947/#review16139
Attachment #8655616 - Flags: review?(felipc) → review+
Comment on attachment 8652387 [details]
MozReview Request: Bug 1189799 - Make sure that about:performance displays each add-on only once (front-end);r=felipe

Bug 1189799 - Make sure that about:performance displays each add-on only once (front-end);r=felipe
Comment on attachment 8652388 [details]
MozReview Request: Bug 1189799 - Make sure that about:performance displays each add-on only once (back-end);r=felipe

Bug 1189799 - Make sure that about:performance displays each add-on only once (back-end);r=felipe
Comment on attachment 8655616 [details]
MozReview Request: Bug 1189799 - Make sure that about:performance displays each add-on only once (more tests);r=felipe

Bug 1189799 - Make sure that about:performance displays each add-on only once (more tests);r=felipe
Attachment #8655616 - Attachment description: MozReview Request: Bug 1189799 - Make sure that about:performance displays each add-on only once (more tests);r?felipe → MozReview Request: Bug 1189799 - Make sure that about:performance displays each add-on only once (more tests);r=felipe
(In reply to David Rajchenbach-Teller [:Yoric] (use "needinfo") from comment #18)
> Comment on attachment 8655616 [details]
> MozReview Request: Bug 1189799 - Make sure that about:performance displays
> each add-on only once (more tests);r=felipe
> 
> Bug 1189799 - Make sure that about:performance displays each add-on only
> once (more tests);r=felipe

Hey Yoric, this failed to apply:

patching file toolkit/components/perfmonitoring/AddonWatcher.jsm
Hunk #1 FAILED at 159
1 out of 1 hunks FAILED -- saving rejects to file toolkit/components/perfmonitoring/AddonWatcher.jsm.rej
patch failed to apply
abort: fix up the merge and run hg transplant --continue

could you guys take a look ? thanks!
Flags: needinfo?(dteller)
Comment on attachment 8652387 [details]
MozReview Request: Bug 1189799 - Make sure that about:performance displays each add-on only once (front-end);r=felipe

Bug 1189799 - Make sure that about:performance displays each add-on only once (front-end);r=felipe
Comment on attachment 8652388 [details]
MozReview Request: Bug 1189799 - Make sure that about:performance displays each add-on only once (back-end);r=felipe

Bug 1189799 - Make sure that about:performance displays each add-on only once (back-end);r=felipe
Comment on attachment 8655616 [details]
MozReview Request: Bug 1189799 - Make sure that about:performance displays each add-on only once (more tests);r=felipe

Bug 1189799 - Make sure that about:performance displays each add-on only once (more tests);r=felipe
I seem to have a conflict somewhere. Investigating.
Flags: needinfo?(dteller)
Comment on attachment 8655616 [details]
MozReview Request: Bug 1189799 - Make sure that about:performance displays each add-on only once (more tests);r=felipe

Bug 1189799 - Make sure that about:performance displays each add-on only once (more tests);r=felipe
Yoric, so you only want to have attachment 8655616 [details] checked-right not the other 2 ones or ?
Flags: needinfo?(dteller)
No, it's all three of them, why?
Flags: needinfo?(dteller) → needinfo?(cbook)
(In reply to David Rajchenbach-Teller [:Yoric] (use "needinfo") from comment #28)
> No, it's all three of them, why?

hm for the first checkin-request there seems to be problem and don't apply to fx-team cleanly:

patching file toolkit/components/aboutperformance/content/aboutPerformance.js
Hunk #2 FAILED at 73
Hunk #3 FAILED at 296
2 out of 8 hunks FAILED -- saving rejects to file toolkit/components/aboutperformance/content/aboutPerformance.js.rej
patch failed to apply


could you take a look, thanks!
Flags: needinfo?(cbook) → needinfo?(dteller)
Comment on attachment 8652387 [details]
MozReview Request: Bug 1189799 - Make sure that about:performance displays each add-on only once (front-end);r=felipe

Bug 1189799 - Make sure that about:performance displays each add-on only once (front-end);r=felipe
Comment on attachment 8652388 [details]
MozReview Request: Bug 1189799 - Make sure that about:performance displays each add-on only once (back-end);r=felipe

Bug 1189799 - Make sure that about:performance displays each add-on only once (back-end);r=felipe
Comment on attachment 8655616 [details]
MozReview Request: Bug 1189799 - Make sure that about:performance displays each add-on only once (more tests);r=felipe

Bug 1189799 - Make sure that about:performance displays each add-on only once (more tests);r=felipe
Flags: needinfo?(dteller)
This should now be fixed.
Flags: needinfo?(cbook)
(In reply to David Rajchenbach-Teller [:Yoric] (use "needinfo") from comment #34)
> This should now be fixed.

yeah thanks Yoric!
Flags: needinfo?(cbook)
Depends on: 1328254
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: