Search Issue Tracker
By Design
Votes
0
Found in [Package]
10.4.0
Issue ID
1314181
Regression
No
[HDRP] CPU usage increases significantly (4 - 5ms) when the Render Graph is used
How to reproduce it:
1. Open the attached project "1314181.zip"
2. Load the "TestScene" Scene
3. Set Profile Analyzer's Mode to 'Compare' and click on 'Open Profiler Window' in the Profile Analyzer window (Menu > Window > Analysis > Profile Analyzer)
4. Uncheck the 'Use Render Graph' checkbox in the HDRP Default Settings (Menu > Edit > Project Settings > HDRP Default Settings)
5. Enter the Play Mode
6. Wait few seconds, and in the Profile Analyzer window click the blue 'Pull Data' button
7. Leave the Play Mode
8. Check the 'Use Render Graph' checkbox in the HDRP Default Settings
9. Enter the Play Mode
10. Wait few seconds, and in the Profile Analyzer window click the red 'Pull Data' button
11. In the Profiler Analyzer window in the 'Top 10 markers on median frames' select 'DoRenderLoop_Internal()' marker
12. Compare CPU usage in Marker Summary section in Profiler Analyzer
Expected result: It takes around the same time (difference ~1ms) to render the Scene when Render Graph is used and it is not used
Actual result: It takes more time (4 - 5ms) to render a Scene when the Render Graph is used
Reproducible with: 10.1.0, 10.2.0 (2020.2.0b12), 10.3.2 (2020.2.3f1), 10.4.0 (2020.3.4f1)
Could not test with: 7.5.3 (2019.4.24f1) (Render Graph is not introduced yet), 11.0.0 (2021.1.0b6), 12.0.0 (2021.2.0a13) (cannot compare CPU usage due to not existing 'Use Render Graph' option)
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note:
Currently this is not due to a bug, but indeed we need to optimize rendergraph overhead and said optimization task is in our backlog.