Open Bug 1582621 Opened 5 years ago Updated 2 years ago

Scene building takes too long (> 7ms) on the MotionMark 1.1 Multiply benchmark

Categories

(Core :: Graphics: WebRender, defect, P3)

Product:
Core
Component:
Graphics: WebRender
Type:
defect

Tracking

()

People

(Reporter: mstange, Unassigned)

References

(Blocks 2 open bugs)

Details

Profile: https://perfht.ml/31D0v7L

On the "MotionMark :: Multiply" benchmark on https://browserbench.org/MotionMark1.1/developer.html , the sum of RefreshDriver tick + scene building exceeds 16ms even on small work loads, so we can never keep up 60fps.
Bug 1566826 is about the slow display list building part. This bug is about the slow scene building part.
(We cannot take advantage of the pipeline parallelism between the main thread and the scene builder thread to get 60fps because we don't allow the main thread to get more than 2 frames ahead of rendering.)

I wonder if this is a regression.

The priority flag is not set for this bug.
:jbonisteel, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jbonisteel)
Flags: needinfo?(jbonisteel)
Priority: -- → P3
Blocks: wr-scene-building-perf
No longer blocks: wr-perf
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.