MacOS isn’t more memory efficient, you can’t be when using 16KiB pages vs 4KiB. That’s a lot of wasted memory.

My experience running multiple bloated Java JetBrains IDEs, Chrome with 50+ tabs, begs to differ.

Reread my comment. Yes, macOS (or ARM, here) wastes memory. For every 1KiB page you have, you're wasting 15KiB of memory.

That's just how this works. It's a performance vs. efficiency tradeoff.

And there's nothing special about your workload. It's small in comparison to many others that many other OSes on many other ISAs, including Windows & x86 w/ AWE, have been running for quite some time with no issue.

	▲	tredre3 2 days ago \| parent [-]
		> For every 1KiB page you have, you're wasting 15KiB of memory. Applications do not allocate memory through the kernel, though. There's a layer between the application code and the kernel, usually the libc or equivalent, that takes the page and fills it with smaller allocations. And most allocators out there usually request pretty big chunks at a time too, measured in megabytes/hundreds of pages. So what you are saying might be technically true if you were to dispatch all mallocs to the kernel, it is not actually true in the real world.

▲

udev4096 3 days ago | parent | prev [-]

[flagged]

▲

udev4096 3 days ago | parent | prev [-]

It's definitely not. I use mac pro for work and it chugs around 16GiB (out of 64) of RAM on IDLE! It also has the worst keyboard I have ever used with a crazy big trackpad which I absolutely hate

	▲	saagarjha 2 days ago \| parent [-]
		I don't think you understand how memory accounting works on modern OSes? When the machine is idling, it will have a bunch of stuff in RAM because why wouldn't it?