All you've got is vague feedback that "the app is slow." How do you approach that with Instruments?
First sort the symptom into an axis (CPU, memory, rendering, or I/O), run the matching template on a real device in a Release build to get numbers, then fix and re-measure the same scenario.
Performance and debuggingMultiple choiceIntro
Tapping a certain button freezes the screen for about a second. To see which function on…
#instruments #time-profiler
Performance and debuggingShort answerExpert
You run Time Profiler and 80% of main thread time lands in CA::Transaction::commit or…
#instruments #time-profiler
Performance and debuggingShort answerBasics
Opening and closing a certain screen repeatedly makes the app's memory keep growing. In…
#instruments #allocations
Performance and debuggingShort answerBasics
Someone reports that search results take too long to appear. Instead of printing…
#instruments