Dave Rudisill <> wrote in
news::
> For those of us who saw a recent Computer World article claiming
> that "Most Windows 7 PCs max out memory", I see that Win7News has
> just pointed to a couple articles discrediting the "finding":
>
> <http://www.osnews.com/story/22896/Wi..._FUD_Explained
> > <http://blogs.zdnet.com/BTL/?p=31024>
>
> Computer World has left the story on line, with a disclaimer:
> <http://www.computerworld.com/s/artic...ows_7_PCs_max_
> out_memory>
>
Huh. Looks like they got serious egg on their faces. I'm looking at my
machine, Win7 64 bit, 4GB ram.
Used: 2250
Cached: 1830
Available: 1836
Free: 41
They look at free, not available, and came to some bad conclusions.
I just loaded an ~80MB file into memory, and this is how it changed.
Used: 2341 (+91)
Cached: 1780 (-50)
Available: 1755 (-81)
Free: 4 (-37)
(the above numbers fluctuate a bit, but not by much. As I typed this,
available went up to 1763, free went up to 16)
Used memory went up 91MB, pretty much expected. Cached went down 50, free
went down 37. It looks like it took everything that was "free", and then
started taking cached to make up the difference. All of this was
lightning fast. If I load 500MB into memory, it takes it out of cached -
lightning fast. If I unload it, it goes into free. And then free slowly
drops and cached slowly increases until it reaches some sort of
equilibrium. Very interesting.
So, yeah, they seriously screwed up by crying the sky is falling before
taking the time to do their homework.