How to reproduce:
1. Open the “GapTinyJobs.zip“ project
2. Build and run the project
3. Move the Slider to the left side (to set worker thread count to 1)
4. Observe the “Mean ms” and “Mean fps” data under the slider in the Player
5. Move the Slider to the right side (to set worker thread count to the maximum possible number)
6. Observe the “Mean ms” and “Mean fps” data under the slider in the Player
Expected results: With maximum worker threads the “Mean ms” is lower and the “Mean fps” is higher than with 1 worker thread
Actual results: With maximum worker threads the “Mean ms” is higher and the “Mean fps” is lower than with 1 worker thread
Reproducible in: 2021.3.41f1, 2022.3.39f1, 6000.0.12f1
Reproduced on: Windows 11 Pro (23H2), macOS 14.5 (by the reporter)
Not reproduced on: No other environment tested
Notes:
- Also reproducible in the Editor
- This is suspected to be an issue affecting all platforms
- Most of the time the worker threads are idling
- A lot of gaps are present between jobs in multiple worker threads
- By default the worker thread count is set to maximum, meaning all users are experiencing worse performance by default