Search Issue Tracker
Fixed in 1.3.0 Preview 8
Votes
0
Found in [Package]
1.2.0 Preview
Issue ID
1186429
Regression
No
Burst performance is degraded up to 8 times when number of calculations is reduced
How to reproduce:
1. Open attached project ("BurstPerformance.zip")
2. Open Test Runner
3. Open Performance Test Report
4. In Test Runner window press Run All
5. Wait for Tests to finish
6. In Performance Test Report window click refresh
Expected result: Test 2 median execution time is longer than Test 1
Actual result: Test 2 median execution time is up to 8 times shorter than Test 1
Reproducible with: Burst 1.2.0 Preview 5 (2019.2.7f2, 2019.3.0b5, 2020.1.0a7)
Could not test with: 2019.2.0a10 and lower (missing namespaces errors), 2019.3.0a8 (missing definition errors)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Add comment