3 ms·
I can exhaust my 64GB just opening browser tabs for documentation.
by eyelidlessness 5y ago
I can exhaust my 64GB just opening browser tabs for documentation.
- kaba0 5y agoIn case your statement is only a slight sarcasm: Isn’t that just the OS saying “unused memory is wasted memory”? Most of it is likely cache that can easily be evicted with higher memory pressure.
- kasabali 5y agoIt is the OS saying “unused memory is wasted memory”, and then every other application thinking they're OS and doing the same.
- kaba0 5y agoSince applications have virtual memory, it sort of doesn’t matter? The OS will map these to actual pages based on how many processes are available, etc. So if only one app runs and it wants lots of memory, it makes sense to give it lots of memory - that is the most “economical” decision from both a energy and performance POV.
- kasabali 5y ago> So if only one app runs You answered yourself.
- eyelidlessness 5y agoIt’s a slight exaggeration, I also have an editor open and some dev process (test runner usually). It’s not just caching, I routinely hit >30 GB swap with fans revved to the max and fairly often this becomes unstable enough to require a reboot even after manually closing as much as I can. I mean, some of this comes down to poor executive function on my part, failing to manage resources I’m no longer using. But that’s also a valid use case for me and I’m much more effective at whatever I’m doing if I can defer it with a larger memory capacity.
- kaba0 5y agoWhich OS do you use? It’s definitely not a problem on your part, the OS should be managing it completely transparently.