Hacking with Swift Project 30 – Instruments
Why Stack Overflow recommends it
Stack Overflow users link it when explaining that Instruments profiling and memory-leak checks should be done on a real device rather than the simulator.
Recommended by 3 people across 3 different months, 2016 to 2019.
What it is
Final project in Paul Hudson's free Hacking with Swift series, a 44-minute walkthrough of using Xcode's Instruments profiler on a deliberately buggy iOS app. It covers finding performance and memory problems, with side topics like shadows, image caching and cell reuse.
What people said
Recommends mfaani · 2016-11 · Stack Overflow · on “Is the ios iPhone simulator causing memory usage analysis to swell?”
as a side note, whenever you wanna test using instruments, try using a **real device**, because the macbook pro's simulator may act superior than a real device. See this video [this video]
Recommends Mustafa · 2017-03 · Stack Overflow · on “table view cell issue with dealloc from memory”
i don't know i follow example on the youtube for leaking memory issue the cells is dealloc in that example at the end , [this video] , but in my project not dealloc
Recommends Jim Marquardt · 2019-09 · Stack Overflow · on “Xcode Instruments 10.12.1 showing memory leaks on an default project”
Paul Hudson discussed this in a Hacking with Swift video ( [this video] ). The discussion is about a minute long. The gist of it is that simulators shouldn't be used for profiling. Use a real hardware device for profiling.