Discussion in 'Windows 8' started by ian82, Feb 8, 2014.
You need to login to view this posts content.
looks like you have too much Standby memory, you can use RAMMap to empty it (Empty > Empty Standby List)
yeah but how come so much standby memory? that's a whooping 30 GB of standby memory?!
I also thought that once you run winsat formal, and it detects that you have an SSD, it won't actually allow superfetch to cache stuff (correct me if I'm wrong)
next time this happen you can use RAMMap to check which process is taking so much standby memory (Processes tab)
There is absolutely nothing wrong with the above and running apps to clear Ram is a bad idea.
Your memory is cached as it should be since Vista, unused Ram is a waste and Ram is faster than any HDD or SSD.
You asked this very same topic before, do you have amnesia?
The real answer is superfetch. Google it.
cached memory. The more shared, the better (in speeds terms). But you should stop using s**tty software (like windows ) like webroot, qtorrent, etc. They use a lot the hdd and that is cached. As you can see.
i have same problem solved with RAMMap
Ugh. The ignorance in this thread is astounding. How the hell is this a "problem"? Standby is, for all practical intents and purposes, free. Except it's better than free.
When Windows loads data from disk to memory (any kind of data; a data file, an executable, anything), it uses memory that hadn't previously been used ("free" memory). When it is done with that file, it marks that memory as "standby". The only difference between "standby" and "free" is that the former still contains old data. And if memory is required and there isn't enough "free" memory, "standby" memory is used instead.
Why not clear out that old data when it's done? Well, first, zeroing memory isn't computationally free. The CPU has to do work (though not a lot) to blank out memory, so why do it unless you need to? This way, memory is blanked only when it's actually needed to be blanked and recycled. Second, what if that file is accessed again? Now instead of incurring disk access a second time, the system can just flip that chunk of memory back into active status, with zero disk access.
Basically, this is a common-sense feature of any properly-designed memory management system.
The one and only benefit to clearing standby memory is if you're paranoid about security and want to make sure that sensitive data is wiped from memory (and I say "paranoid" because the kernel will always blank out memory that a program allocates, so forcible access of such latent data requires either kernel-level access or physical access to the RAM module).
This also has nothing to do with Superfetch. The only way in which Superfetch plays a role is that through preemptive file loads, it causes more files to be loaded, which causes memory to be marked as standby at a somewhat faster rate. But even with SF disabled, any system that incurs heavy disk access will quickly reach a point where all free memory is standby.
What enigma said...
It's caching previously used data. It doesn't prevent the future use of the memory. It simply uses the free memory until you need more free memory.
Same old story and same as the OP 's previous thread 4 weeks ago and 100x the same old Q gets asked before.
Only so many times you can be arsed to try explain it so I keep it short and sweet, the Task Manager shows its cached in the above screenshot.
Wonder who above peep is calling ignorant.