The title says what my issue is. Its the only debugging tool that makes no sense to me because its just lots of numbers and buttons I dont know
The new article on Creator Documentation, Using MicroProfiler, makes more sense to the chaos. There’s been a couple of articles on it across all documentation sites but this one has a lot more depth to it than just “big bar = big problem”. The components of the MicroProfiler that you’ll be using most as a developer are documented here as well as how to create custom profiles with profilebegin/profileend.
There is additionally the main MicroProfiler article with additional information and the Tag Table article which has a non-exhaustive list of processes you can find on the profiler. When you enter detailed mode (automatic by pausing), these are the various coloured horizontal bars you can see.
A quick rundown of the important parts:
-
The scroll of orange bars at the top are your frames. Higher bar means longer render time.
-
When in detailed view/paused, you can see active threads and the processes they handle.
-
Labels on the far right are engine threads. See MicroProfiler - Threads.
-
The coloured bar are processes in threads. Longer bars means longer completion time.
-
Vertical height is a hierarchy of code layers (e.g. what happens in current frame’s Stepped).
-
-
Labels (hover over a bar when paused) help point towards a potential problem area.
- Example: you may see a script being very horizontally long. If you hover over it and it has the raycast label, you’ll want to investigate the raycasting being performed in it.
Although MicroProfiler documentation is more expansive now than it was in the past, I do think it still lacks in some areas. Most of the missing documentation right now is mostly for advanced tooling, the components that the majority of developers will be concerned with are there now.
2 Likes