Open Bug 2062897 Opened 3 months ago Updated 3 months ago

Unity-webgl regression with Metal ANGLE

Categories

(Core :: Graphics: CanvasWebGL, defect)

Unspecified
macOS
defect

Tracking

()

People

(Reporter: jnicol, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fxpe])

See these results from the Intel Macbooks on CI: https://perf.compare/subtests-compare-results?baseRev=26bc09ea60f7ad93c8dbc9c53f213c7e6263189d&baseRepo=try&newRev=ccf4b8de8cc70cbc2742b9fc7322ce0f0ea24af2&newRepo=try&framework=13&baseParentSignature=5146680&newParentSignature=5146680&test_version=mann-whitney-u

There is a very large regression in the "Mandelbrot GPU" subtest, and a smaller regression in the "Asteroid Field" subtest

Note we don't run unity-webgl on apple silicon, and attempting to run it locally doesn't work: the framerate for mandelbrot GPU never gets low enough for the test to end!

Whiteboard: [fxpe]

A small part of the Mandelbrot GPU regression can won back by also enabling ANGLE for webrender. This allows us to do a server side wait on webgl content to finish rendering prior to compositing, rather than a client side wait.

That nearly brings us in line with Chrome from my testing. Given that we don't generally perform worse with angle than native GL on GPU bound workloads (e.g. this), I think the remaining regression can therefore be attributed to an increased GPU workload when running on Metal. A large chunk of this is for sure due to ANGLE's ensureLoopForwardProgress flag, which inserts a volatile variable assignment to every loop iteration (and this test's fragment shader contains a huge loop). Avoiding that halves the regression, but unfortunately isn't something we should do.

So I think this is mostly an unavoidable regression, and not worth worrying about too much as it's quite an extreme test case

Rating as S2 because performance regressions on popular game engines seem fairly bad.

Severity: -- → S2

I don't think I'd rate it that high - I doubt this test is particularly representative

You need to log in before you can comment on or make changes to this bug.