If you know your most used/most time consuming function you, at least, have a way of knowing where potential time savings are.
Looking at a function which takes 0-5ms and is called once won't be high on your optimisation lists even if you save 1 ms.
If you have a function which takes 1000 ms and is called
every loop (or every nth loop) and you save 50ms it's a better use of time.
Just an idea, how about creating a small viewport which displays a coloured rect in proportion to the function time to get a graphical output of where you're spending time. Alternatively, save the times to a type and then use that at the end to create a graph of time spent along with the raw data.
Looking at a function which takes 0-5ms and is called once won't be high on your optimisation lists even if you save 1 ms.
If you have a function which takes 1000 ms and is called
every loop (or every nth loop) and you save 50ms it's a better use of time.
Just an idea, how about creating a small viewport which displays a coloured rect in proportion to the function time to get a graphical output of where you're spending time. Alternatively, save the times to a type and then use that at the end to create a graph of time spent along with the raw data.