Search Issue Tracker
Duplicate
Duplicate in 2022.2.X
Votes
1
Found in
2022.2.0b3
Issue ID
UUM-13905
Regression
No
BatchRendererGroup draws have poor thread load balancing in some cases
A user on the forum reports that BatchRendererGroup is taking longer than GameObjects for their workload. The issue seems to be that even though BRG is taking less time per draw, the work is poorly balanced across threads and it takes longer for the thread to finish compared to GameObjects.
Forum post: [https://forum.unity.com/threads/new-batchrenderergroup-api-for-2022-1.1230669/page-3#post-8362923]
Repro project: [https://drive.google.com/drive/folders/1jSzeAgL9FlBtcRWOEDyZefqk5ykTUOVb?usp=sharing]
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
This issue is fixed in 2022.2.0b15 and later.
Duplicate of another internal issue: UUM-16378: BatchRendererGroup performs poorly because of locking during draw command processing
Resolution Note (2022.2.X):
This issue is fixed in 2022.2.0b15 and later.
Duplicate of another internal issue: UUM-16378: BatchRendererGroup performs poorly because of locking during draw command processing