Imagine a messy accounting system. A joke says that "EBITDA" means "earns before I trick d*** auditor" based on the complications accounting has. But there isn't any "tricking" purpose here, just messy concepts. Instead of managing just sales, incomes, costs, cash, revenue etc from where you could do easy equations, they do things like [kidding](-sales +- sqrt(sales^2 - 4·income·costs)/(2·income)[/kidding] if its useful or frequent, and these mixes replace the most "straightforward" concepts.
Accounting "complications" have good reasons, like in the "provisión(es)" and "dotaciones" system (in English accounting "provisiones" seems to be provisions, but for "dotación" -each expense that goes to a provision- I cannot get a sure translation, candidates seem to be provisioning, endowment, allowance and allocation).
Fortunately there's one straightforward concept that survives: committed memory. This is the total use of memory including RAM and used pagefile. If one has disabled the pagefile, this amount must be lower than the usable or whatever name physical RAM b/c in that case it can only be in RAM (that seems to be 7.8 GB here adding "In use" 5.0 GB and "Available" 2.8 GB, physical RAM here is 8 GB; if I disabled the pagefile my "committed limit" would be those 7.8 GB as the hw needs some). My Committed now is 6.2 GB.
Now the sums I cannot do for the "complications"... succeeded unless it's a coincidence. Committed 6.2 GB and RAM in use 5.0 GB means a pagefile.sys of at least 1.2 GB. My pagefile.sys is about 4 GB now, why the additional 2.8 GB? Well, I have exactly 2.8 GB "Cached". As it isn't "Committed" it is "dispensable" (just an English word unless I've hit a technical term), but ready (not necessarily all at the same time) to be "committed" fast.
In my Windows 10 system I have 32 GB and I have disabled the pagefile, the same as in a Windows 7 with 16 GB. This is risky specially compared to enabling it with "infinite" C: free space, but with large amounts of RAM Windows tends to waste disk space in caching. Technically (RAM prices apart) doing builds with RAM excess and disabling the pagefile is a good strategy.
