DWrite contention on worker threads is too high
Categories
(Core :: Graphics: WebRender, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox69 | --- | fixed |
People
(Reporter: jrmuizel, Assigned: lsalzman)
References
Details
Attachments
(2 files)
This shows up when profiling https://static.mozilla.com/moco/en-US/images/mozilla_eoy_2013_EN.svg
Reporter | ||
Updated•6 years ago
|
Comment 2•6 years ago
|
||
Related: bug 1533545, limiting the amount of worker threads would probably help here as well.
I should post a profile of this.
Would be wonderful!
Reporter | ||
Updated•6 years ago
|
Assignee | ||
Comment 3•6 years ago
|
||
Comment 5•6 years ago
|
||
bugherder |
Updated•6 years ago
|
Comment 6•6 years ago
|
||
Noticed some perf improvements:
== Change summary for alert #20967 (as of Thu, 16 May 2019 10:47:40 GMT) ==
Improvements:
9% tabswitch windows7-32-shippable opt e10s stylo 12.08 -> 11.02
For up to date results, see: https://treeherder.mozilla.org/perf.html#/alerts?id=20967
Assignee | ||
Comment 7•6 years ago
|
||
Assignee | ||
Comment 8•6 years ago
|
||
Comment on attachment 9066795 [details]
Backed out changeset 6440419b9d33 (Bug 1533546). r?jrmuizel
Beta/Release Uplift Approval Request
- User impact if declined: Frequent crashes for Windows users as observed in bug 1552687.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- 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 backs out a patch that was an experimental performance change that wasn't intended to make it into 68 beta in the first place. It just somehow got landed in 68 due to the weird timing of the train delay. Incorporating this backout just puts us back to where we started at, without the performance change that is regressing stability noticeably.
- String changes made/needed:
Comment 10•6 years ago
|
||
Comment on attachment 9066795 [details]
Backed out changeset 6440419b9d33 (Bug 1533546). r?jrmuizel
backout to fix a stability regression, approved for 68.0b4
Sebastian, heads-up because this won't show up on the uplift query and I'm not sure how to handle the flags...
![]() |
||
Comment 11•6 years ago
|
||
uplift |
You can use the whiteboard and set it to [checkin-needed-beta].
https://hg.mozilla.org/releases/mozilla-beta/rev/290e613b8b2211e41209565318a63cafe0671082
![]() |
||
Updated•6 years ago
|
![]() |
||
Comment 12•6 years ago
|
||
Comment 13•6 years ago
|
||
Assignee | ||
Comment 14•6 years ago
|
||
Bug 1552687 should fix the underlying race condition that this bug aggravated. I relanded the original patch just so that we can purposely kick up potential crashes, and hopefully not actually crash anymore at all to verify that bug 1552687 fixed it. If it starts getting bad again, we can reland the backout. The important thing is that we meanwhile have it backed out of beta while we are trying to resolve and collect data on the issue.
Comment 15•6 years ago
|
||
If I understand this correctly, this would also really help us out with bug 1483436.
Assignee | ||
Comment 16•6 years ago
|
||
(In reply to Ryan Hunt [:rhunt] from comment #15)
If I understand this correctly, this would also really help us out with bug 1483436.
It should, yes, if we can manage to resolve the race condition that is blocking us on this.
Comment 17•6 years ago
|
||
bugherder |
Comment 18•6 years ago
|
||
Comment on attachment 9066795 [details]
Backed out changeset 6440419b9d33 (Bug 1533546). r?jrmuizel
clearing approval on the backout so this doesn't show up on uplift queries
Description
•