Profiling with Tracy

[j-jorge]

In #2495 we discussed solutions for frame-level profiling and I suggested to use Tracy. I did a build of my app where I have instrumented some functions from Axmol and I think it is quite instructive. Here is a capture where I have selected all frames:

It shows the rendering statistics that we can also get when using ax::Director::setStatsDisplay(), except that here I can see the evolution during the game.

At the top there are some red ticks, those are the frames that took too much time. By clicking on one of these marks I can see what was happening in the instrumented functions:

The problem is the creation of the missing glyphes for the labels.

I'm discovering the tool and it seems great so far. I especially appreciate that it can profile the game as it is running on my phone. Nevertheless it is quite intrusive.

You can see the changes I made to Axmol in this commit from my fork.

Do you think it would be a useful addition to Axmol? In particular, I did not add the Tracy library in the third-parties as it is a quite large dependency, plus it also needs a client application to request the profiled program. In my case I install those upfront then I ask Axmol to find it using CMake's find_package.