The caveats are what made this worth reading — simulator, not a phone, and the first-frame timing leaning one way. Too many benchmark posts bury that part.

The debugging point landed hardest for me. A breakpoint that shows the one call that changed the text, with a stack that leads back to your own code, is worth a lot when something breaks at the worst time. Faster frames are nice, but being able to find the problem quickly is what actually saves a day.