In Time Profiler, the top entries on the scrolling hot path are swift_retain, swift_release, and swift_bridgeObjectRetain. Why does this happen?
Every time you pass reference types, existentials, or closures in a hot loop, the compiler inserts atomic retain/release calls. That's ARC traffic: the CPU is spending more on ownership bookkeeping than on the real work.
Performance and debuggingShort answerBasics
All you've got is vague feedback that "the app is slow." How do you approach that with…
#time-profiler
Performance and debuggingMultiple choiceIntro
Tapping a certain button freezes the screen for about a second. To see which function on…
#time-profiler
Performance and debuggingShort answerBasics
You're asked to "optimize this function, it's slow." What do you do before you touch the…
#optimization
Performance and debuggingShort answerExpert
You run Time Profiler and 80% of main thread time lands in CA::Transaction::commit or…
#time-profiler