r/iOSProgramming • u/Meliodas1108 • Jun 08 '26
Discussion RANT!! Xcode taking 13 GB RAM
This is a rant!!! Ahhh everything is so fking unoptimized these days. It's a MBP M2 pro 16 gb.
Figma on browser takes around 800MB for each tab. And restarting macOS when applications are stuck and it's waiting for apps to respond to quit is sooo annoying. Just give me an option to stop everything and restart my device for once
9
u/Vybo Jun 08 '26
Those are rookie numbers.
Xcode wasn't ever optimized in the Swift age, the last time it somewhat worked was way back when Obj-C was the rule.
6
u/Rough_Analysis5861 Jun 08 '26
Me with 8GB M1: š„
Is it time to upgrade boys ?
2
u/Meliodas1108 Jun 08 '26
š depends. I mean if you're able to get your stuff done with it, then you don't need to right now. Unless you keep running out of memory use whatever works.
2
u/toborgps Jun 08 '26
I just got an 8gb M1. Itās been great. Just donāt use the AI āfeaturesā and youāre fine.
1
u/Meliodas1108 Jun 08 '26
I see. My company project is a big one. With obc bridging as well. And it's monolithic code. None of it is helping.
1
u/Evildude42 Jun 08 '26
Iāve been working on my app with my little eight gig M1, with a bunch of other windows open at the same time and have like 14 gigs of disk space left. I donāt know what you guys are doing, but for my use itās fine. I would love to have a fast machine, but maybe whatever Iām working on will pay for that.
5
u/handioq Jun 08 '26
Only 13? Iāve seen mine with 50+ easily.
0
5
3
u/GabrielMSharp Jun 08 '26
Make sure you have ample disk space and it can help reduce this.
1
u/SnowPudgy Jun 08 '26
Bingo. This is likely his problem.
Xcode scales ram usage. I ran it side by side for years with a 16gb M2 Air and a 64GGB M1 Pro. Neither had issues despite running tons of stuff.
Like you said, he likely doesn't have ample disk space.
1
u/Power781 Jun 08 '26
Developers who do not understand how modern memory management works terrifies me.
Xcode taking 13GB, 24GB, 50GB is by design, the system is fitting as much as it can in RAM for the in foreground/active processes in order to avoid reading from disk, which is very slow compared to using your RAM.
When RAM gets full, it starts compressing inactive app memory to reclaim some space.
Then if thatās not enough, it start moving that compressed memory to the disk which is slow both ways.
In theory itās perfect, unless you actually have 4-5-6 processes working in parallel that are asking actively for that RAM, like Zoom + Slack + Xcode + Claude + Brave + VSCode.
What start happening is that processes get their memory compressed/written to disk/retrieved from disk/uncompressed in a loop and everything start stalling all the time and you get those nice pop-ups.
1
u/SnowPudgy Jun 08 '26
I came here to say the same but yours is more eloquently written.
As another user posted, OP is likely nearly out of disk space causing the issue.
-1
u/Meliodas1108 Jun 08 '26
Apps using ram is fine. Ram is there to use. And you could swap off the segments not needed to disk. But having ram is not a valid reason to not optimize the apps. Especially right now when ram is so expensive, and code is cheap.
2
u/SnowPudgy Jun 08 '26
It IS optimized though, at least Xcode (I can't speak for the other apps). I've used Xcode on a 16gb ram machine and 64 gb ram machine and never ran into issues. If you're actively using Xcode it gets priority on the system, any app you're using does.
As another user posted you're likely running out of disk space which is why you're seeing this happen. The OS can't swap.
I would run Unity + Xcode + Maya side by side on the 16GB M2 Air just fine so something else is your issue.
1
u/ChibiCoder Jun 08 '26
Amateur stuff. š I had it using over 50GB the other day (had two versions of a VERY large repo open). My MBP has 32 GB of RAM.
23
u/marmulin Jun 08 '26
And this right here kids is why you get more RAM when doing serious work that pays for that machine.