Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

VAO performance issues on Radeon 460

See original GitHub issue

Describe the bug

VAO Test ~5000ms from 1500ms with latest THREE r126 regression to r117.1

Test from https://github.com/mrdoob/three.js/pull/16287 To Reproduce

Steps to reproduce the behavior:

https://jsfiddle.net/s4vwgm2x/ (r126.1) https://jsfiddle.net/s4vwgm2x/1/ (r117.1)

Expected behavior

<1500ms withVAO

Screenshots Bildschirmfoto von 2021-03-23 15-49-42

Platform:

Device: [Desktop]
OS: [ Linux]
Browser: [Chrome]
Three.js version: [r126.1]

Issue Analytics

State:
Created 2 years ago
Comments:37 (9 by maintainers)

Top GitHub Comments

2reactions

kenrussellcommented, Jul 2, 2021

Yes, hopefully this performance problem has been addressed on all platforms. The problem was solely in Chrome, not ANGLE, so I apologize for incorrectly guessing where it was. Please follow up on https://crbug.com/1192082 to confirm whether this is fully addressed. Thanks.

2reactions

kenrussellcommented, Jun 28, 2021

If it’s not too difficult to leave the VAO and non-VAO code paths in place, that would be great - we will absolutely try to optimize the VAO path better in ANGLE in https://crbug.com/1192082 .

Would appreciate it if you’d continue pursuing using UBOs. The implementation of this functionality in ANGLE on top of D3D11 has already received quite a lot of attention in https://bugs.chromium.org/p/angleproject/issues/detail?id=3682 , and I think it should be a performance benefit on all platforms. But if you can try it and let the browser implementers know about any performance pitfalls you have, with test cases, that would be greatly appreciated.