Hey,
I noticed when profiling CPU that the RenderPipelineManager.DoRenderLoop_Internal() is being considered a “Scripts” update instead of a “Rendering” update, why is that?
This is kinda misleading…
1 Like
I believe this is because DoRenderLoop_Internal method is just a C# method that by default gets “Scripts” category. It could be marked as “Render”, but all child methods it calls would more likely stay as “Scripts”, so it would not change the picture much as area is defined but child areas (you can see that there is a small Rendering contribution and methods self time is only 0.09ms)
I would enable deep profiler and look what are the methods that DoRenderLoop_Internal calls and if those really belong to the Rendering. If so, perhaps a bug report would be appreciated, so that we can improve markup to be less confusing
3 Likes
Ah, that makes sense! Thanks for taking the time to reply.
I found weird because this does not always shows up there taking that much cpu time in the exact same scenario.
2 Likes