Profile: https://share.firefox.dev/46snaEW The profile was coolected by Bas: using https://browserbench.org/MotionMark1.2/developer.html - select motionmark/leaves - "Keep at fixed complexity" - set the boz that appears next to motionmark/leaves at 2500 - run The largest bottleneck appears to be the content thread however we spend a fair amount of time on scene building and frame building with timings in the realm of 10-12ms and a large portion of both are in memory allocation/deallocation (mostly growing vectors).
Bug 1857081 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Profile: https://share.firefox.dev/46snaEW The profile was coolected by Bas: using https://browserbench.org/MotionMark1.2/developer.html - select motionmark/leaves - "Keep at fixed complexity" - set the boz that appears next to motionmark/leaves at 2500 - run The largest bottleneck appears to be the content thread however we spend a fair amount of time on scene building and frame building with timings in the realm of 10-12ms and a large portion of both are in memory allocation/deallocation (mostly growing vectors). Chrome is doing better than us at this test, but looks like something webrender should be able to handle pretty well.