3 ms·
Not overcommitting is Windows's default and only behavior A memory allocator can implement overcommit, because you can separate reserving virtual memory and ha
by wongarsu 4mo ago
Not overcommitting is Windows's default and only behavior
A memory allocator can implement overcommit, because you can separate reserving virtual memory and having it backed by physical memory into two different system calls. But from the point of view of the kernel, any time it promises to give you physical memory that memory is backed either by RAM or by space reserved in the swap file
- senfiaj 4mo agoAs I understand, Windows can also lazily allocate pages, but it does after making sure the memory budget is adequate in a case of low physical RAM pressure and is guaranteed to be backed up by a page. But yeah, Linux approach is really sloppy.