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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment