daring blade
Currently there is a lot of visual noise in the profiler when trying to figure out what jobs do.
The example in the image has the following setup:
- B and C have a dependency on A
- D has a dependency on B and C
- E has a dependency on C but also can only run on the main thread.
But trying to find this when looking through the timeline is a pain, and there's so much "Profiler.ParseThreadData" and "Idle" on-screen that it's difficult to parse mentally. If there was a way to filter it to only show jobs and systems it'd be a lot easier to see what actually starts and ends where.
Even better would be a way to see what actually ends up having a dependency on what in some sort of graph. Being able to see visually why a job runs later than another job would be super useful.
