Closed Bug 1421054 Opened 2 years ago Closed 2 years ago
Mark Animometer Multiply is spending 50% of Build Web Render Commands in Recurse And Define Clip
59 bytes, text/x-review-board-request
Profile: https://perfht.ml/2zJJO0C Steps to reproduce: 1. Go to http://browserbench.org/MotionMark/developer.html 2. In the right column, check "Keep at a fixed complexity" 3. In the left column, only check the Animometer: Multiply test, and set its complexity to 400 4. Click "Run benchmark" and profile.
https://searchfox.org/mozilla-central/rev/7a8c667bdd2a4a32746c9862356e199627c0896d/gfx/layers/wr/ScrollingLayersHelper.cpp#360-362 When I wrote this code the thing I had in mind to fix the potential cliff was what I described in bug 1415932, but that turned out to be harder than expected (see comment 1 on that bug). I can try again to see if I can come up with a better way.
I have an idea on how to fix this without going the route of bug 1415932. Picking this up as if it works it will be a big win.
Assignee: nobody → bugmail
Status: NEW → ASSIGNED
Priority: -- → P1
Whiteboard: [wr-mvp] [triage] → [wr-mvp]
I wasn't able to reproduce the problem as described in comment 0, however I did see RecurseAndDefineClip taking up 50% of time on MazeSolver as well, so I used that instead to test. The patch I have drastically improves MazeSolver time (~57 seconds down to ~14 seconds). Try push to make sure it doesn't break anything: https://treeherder.mozilla.org/#/jobs?repo=try&revision=48ec1ceb1bc3aefaafc775ce080ab95efba32d49
For comparison the same build with WR disabled gives me results of ~17 seconds.
Comment on attachment 8932595 [details] Bug 1421054 - Remove performance cliff resulting from linear search through clips. https://reviewboard.mozilla.org/r/203652/#review209514
Attachment #8932595 - Flags: review?(mstange) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/92847636d7b1 Remove performance cliff resulting from linear search through clips. r=mstange
You need to log in before you can comment on or make changes to this bug.