6 ways to reduce Xcode RAM usage
1 Clean DerivedData regularly
Run 'rm -rf ~/Library/Developer/Xcode/DerivedData' to clear build caches. This forces a clean re-index which can fix SourceKit memory bloat.
2 Quit unused simulators
Each running iOS simulator consumes 500 MB–2 GB. Close simulators you're not testing against. Use 'xcrun simctl shutdown all' to kill all simulators at once.
3 Limit open projects
Each open Xcode workspace runs its own SourceKit instance. Close projects you're not actively editing.
4 Disable automatic previews
SwiftUI previews spawn preview agents that consume memory. Disable automatic preview refresh and only trigger when you need to see the result.
5 Reduce indexing scope
For large projects, consider excluding test targets and dependencies from indexing when you're not working on them.
6 Restart Xcode after long sessions
SourceKit's memory tends to grow during long editing sessions. Restarting Xcode every few hours during heavy development reclaims significant memory.
How DevPulse helps with Xcode
DevPulse groups Xcode's constellation of processes — SourceKit, build daemons, simulators, preview agents — into one unified view. It tracks which subprocess is consuming the most and detects zombie preview agents.
Instead of guessing how much RAM Xcode consumes or manually checking Activity Monitor, DevPulse gives you a clear, always-visible answer in your menu bar.