Reading the Time Profiler call tree
You run Time Profiler and 80% of main thread time lands in CA::Transaction::commit or UIKit internals. Your own code doesn't show up. How do you read this result?
You run Time Profiler and 80% of main thread time lands in CA::Transaction::commit or UIKit internals. Your own code doesn't show up. How do you read this result?
Time Profiler is sampling based, so system frames sit at the top. Strip them with Hide System Libraries, Invert Call Tree, and Heaviest Stack Trace, walk down to the first frame that's your code, and read Self and Total time separately.
Performance and debuggingShort answerBasics
All you've got is vague feedback that "the app is slow." How do you approach that with…
#time-profiler #instruments
Performance and debuggingMultiple choiceIntro
Tapping a certain button freezes the screen for about a second. To see which function on…
#time-profiler #instruments
Performance and debuggingShort answerBasics
Someone reports that search results take too long to appear. Instead of printing…
#instruments
Performance and debuggingMultiple choiceAdvanced
You recorded scrolling with the Instruments Animation Hitches template. Which statements…
#instruments