OS Memory Management
Cluster debates operating system handling of RAM and virtual memory, including why OS uses nearly all available RAM for caching and page cache, virtual vs physical memory distinctions, and whether applications should manage memory instead of the kernel.
Activity Over Time
Top Contributors
Keywords
Sample Comments
i can't help but wonder if this has been tested vs. just letting the os virtualise memory for you... i'm assuming yes.
Considering he's got a 16GB of RAM, this is virtual memory, and most programs don't need to keep it all loaded at all times (if they do, you'll notice with constant paging exception handling).
Memory does not work the way you imagine it does. OS do not optimize for keeping memory empty.
If your OS is running totally in virtual memory instead of mostly RAM I see a problem.
Because it isn't taking RAM for its own use.
Virtual memory should be handled by the operating system not re-implemented by each application.
I'm curious - what's the benefit of doing this sort of thing at the application level, rather than letting the OS's virtual memory system handle it as usual?
Are you sure that isn’t file cache and such? The OS uses as much of it as it can.
Why? Reserving virtual memory has nothing to do with actual memory usage.
Why do applications think they can manage my memory better than my kernel?