Back in the olden days of blitz basic on the Amiga, a common trick to see how your code was performing was to poke the border color at the start of a chosen loop, then poke it back again at the end of it. (or something along those lines.. it was a very long time ago!)
This would give you a very quick & dirty visual guide as to how much of a frame each of your functions was taking up, depending on how much of the border was colored, and hence what was worth optimising and what wasn't (I'm finding I can be incredibly lazy with an I5 compared to a motorola 68020!)
Is there a similar trick for AppGameKit that anyone knows of?
