Daily iOS
Performance and debugging

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?

How would an interviewer hear this answer? You'll see whether they'd move on, dig in, or say no, and which sentences would trip you up. Your score doesn't change.
See the short answer

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.

Share a question