superfetch option not showing in services but disabled in regedit.
but still getting full cache at startup without opening programs !!
it's hanging,lagging and crashes!!
Last edited by remostalin; 11 Nov 2018 at 07:02.
That is the ideal memory display. This is the way a modern operating system is designed to work.
Available memory can be in 2 states, displayed as cached or free. Cached memory is making a contribution to performance while free memory is wasted. It is like employees of a company on a perpetual coffee break, contributing nothing but still collecting their paycheck.
Windows 10 does not need and will not benefit from "Memory Optimizer Pro" or other programs like it.
I don't know what the lagging problem is but it isn't due to memory.
I do not think, it is showing the correct value, task manager shows, how much memory is cached.
You can clear it with Process Hacker for free, at least for testing, I had 3GB, now it shows 62MB.
By the way, you can try something like Mem Reduct or CleanMem.
Memory Optimiser Pro is bloatware, gives even less information than the Windows Task Manager. No point at all, uninstall.
It maybe that or something else causing your problems.
Your RAM is not "too full", it is meant to be used, if there is not enough then a paging file on your HDD is used. No problem, that is supposed to happen, just part of Windows memory management.
Part of the lagging is likely to be caused by stopping of Prefetch and/or Super Prefetch the point of which is to speed up the loading of applications.
Put two managers on one job and what do you get...
The cached value will vary widely depending on how long the system has been running, the current workload, what it was recently, and more. 1.7 GB is certainly a reasonable value. Cached memory is good and the higher the better. Free memory should be low, zero being the optimum value.
If you are having performance problems you are looking in the wrong place.
Yes. I currently have only 60MB actually free, with 1.7GB cached. Typically cached memory holds code that is not in use, but it is there to save time reading it from disk again if you ever need to use it. Should your programs need more memory the cached code will be discarded and the memory will be used by your program.
Quote
