imgLoader::NotifyObserversForCachedImage is slow
Categories
(Core :: Graphics: ImageLib, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox96 | --- | wontfix |
firefox97 | --- | wontfix |
firefox98 | --- | fixed |
firefox99 | --- | fixed |
People
(Reporter: emilio, Assigned: sefeng)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
48 bytes,
text/x-phabricator-request
|
pascalc
:
approval-mozilla-beta+
|
Details | Review |
On pages that frequently hit the network cache like bug 1753453, we spend a lot of time on this function, see bug 1753453 comment 11.
This is only for devtools and is supposed to run at most once per page per image, but instead we run it all the time and filter it on devtools' side (bug 1747494).
Updated•3 years ago
|
Updated•3 years ago
|
Comment 1•3 years ago
|
||
Set release status flags based on info from the regressing bug 1722759
Updated•3 years ago
|
Updated•3 years ago
|
Assignee | ||
Comment 2•3 years ago
|
||
Agreed, yeah. We fixed it on the devtools side, but it's a shame that I didn't mention we should fix it on the platform side...
I don't know if Emilio is going to submit a patch, but I can definitely make one. So I'll leave my NI for now.
Comment 3•3 years ago
|
||
Set release status flags based on info from the regressing bug 1722759
![]() |
||
Updated•3 years ago
|
Assignee | ||
Comment 4•3 years ago
|
||
I've also tested the behavior in Chrome and I think this is
the correct way of doing it. Chrome also only notifies the
cached entry once, it won't notify it even if I manually
trigger it after pageload.
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Comment 6•3 years ago
|
||
bugherder |
Comment 7•3 years ago
|
||
Do you think this would be a good candidate to uplift?
Assignee | ||
Comment 8•3 years ago
|
||
Yeah, I noticed the profile in bug 1754908 has a lot of http-on-image-cache-response
, so this patch has some potentials, I agree we should uplift.
Assignee | ||
Comment 9•3 years ago
|
||
Comment on attachment 9263141 [details]
Bug 1753471 - Only notify http-on-image-cache-response once per cache entry r=tnikkel
Beta/Release Uplift Approval Request
- User impact if declined: Users may experience degraded performance when they visit certain sites (If the sites reused a lot of cached images)
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This is not risky because the changes were only about preventing an notification from firing and the notification is only being used for devtools.
- String changes made/needed:
Comment 10•3 years ago
|
||
Comment on attachment 9263141 [details]
Bug 1753471 - Only notify http-on-image-cache-response once per cache entry r=tnikkel
Safe fix in early betas for a perf regression that may also fix a webcompat P1 bug (bug 1754908), approved for 98 beta 5, thanks.
Comment 11•3 years ago
|
||
bugherder uplift |
Description
•