> Now why would you want to know the committed memory over the actual physical RAM in use?
Because in Windows, committed size is relative to physical size. You can commit a lot more than RAM, but watch your page-file grow.
malloc() can fail on Windows for this reason. This is not the same on Linux or any of the BSD's I've tried. :)
I experienced/discovered this August last year.. sometimes understanding a lot about Linux can make you blind to the architectural differences Windows has.
> Now why would you want to know the committed memory over the actual physical RAM in use?
Because in Windows, committed size is relative to physical size. You can commit a lot more than RAM, but watch your page-file grow.
malloc() can fail on Windows for this reason. This is not the same on Linux or any of the BSD's I've tried. :)
I experienced/discovered this August last year.. sometimes understanding a lot about Linux can make you blind to the architectural differences Windows has.
I wrote some cross-platform CPP to show it[0]
[0]: https://gist.github.com/dijit/cb2caa1a40d48e03613f5af0e518d6...