Search Issue Tracker
Fixed
Fixed in 2022.3.40f1, 6000.0.12f1, 7000.0.0a1
Votes
10
Found in
2022.3.33f1
6000.0.6f1
Issue ID
UUM-73194
Regression
Yes
Job allocator contention causes slow job execution
[https://discord.com/channels/489222168727519232/1229522160364683305/1232438969606606972]
A simple job chain where job B depends on job A exposes a serious performance problem when scheduled as a batch. Many jobs will execute and start calling job complete which causes the job index to be freed. However, the job allocator itself is not contention free and we end up hitting the same cache line and serializing all execution which leads to significant execution overhead.
Steps to reproduce:
1.
2.
3.
Actual results:
Expected results:
Reproducible with versions:
Not reproducible with versions:
Can’t test with versions:
Tested on (OS):
Notes:
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Add comment