Author Topic: Metafile - uses 14+ GB of RAM. (Read 16047 times)

makinero · « **on:** November 28, 2015, 07:30:24 am »

Metafile - uses 14+ GB of RAM.
I have a 16 GB (physical) and shows 99% of RAM (in use).
How to safely fix reduce usage?

Shane · « **Reply #1 on:** December 01, 2015, 08:08:00 pm »

Quote

“” Metafile is part of the system cache and consists of NTFS metadata. NTFS metadata includes the MFT as well as the other various NTFS metadata files… In the MFT each file attribute record takes 1KB and each file has at least one attribute record. Add to this the other NTFS metadata files and you can see why the Metafile category can grow quite large on servers with lots of files ”

Found a few things you can try
http://serverfault.com/questions/325277/windows-server-2008-r2-metafile-ram-usage
and
https://social.technet.microsoft.com/Forums/windowsserver/en-US/80c045fc-32ff-4b7f-90ce-545e8bd95138/server-2008-r2-metafile-as-seen-from-sysinternals-rammap-increases-memory-usage-rapidly?forum=winservergen

My free cleanmem program on my other site also can empty the file cache as well.

Shane

makinero · « **Reply #2 on:** December 02, 2015, 04:48:49 am »

Shane - Articles refer to Windows Server 2008 R2

Quote

Found a few things you can try
http://serverfault.com/questions/325277/windows-server-2008-r2-metafile-ram-usage
and
https://social.technet.microsoft.com/Forums/windowsserver/en-US/80c045fc-32ff-4b7f-90ce-545e8bd95138/server-2008-r2-metafile-as-seen-from-sysinternals-rammap-increases-memory-usage-rapidly?forum=winservergen

I use Windows 7.

Shane · « **Reply #3 on:** December 08, 2015, 01:55:28 am »

Windows 2008 R2 is the windows 7 version of server, the same things will work on it as well.

Shane

makinero · « **Reply #4 on:** December 08, 2015, 04:31:53 am »

No always work... can install this service, change the settings in the registry, still use 90-99% RAM

Windows 7 requires an additional complicated script - It's not that simple!

jraju · « **Reply #5 on:** December 10, 2015, 04:57:08 am »

Hi, Mak
Please go to empty tab at the top of systinter tool and then click on “Empty System Working Set” Find the difference it shows in meta file in ram map

makinero · « **Reply #6 on:** December 10, 2015, 08:49:06 am »

Quote from: jraju on December 10, 2015, 04:57:08 am

“Empty System Working Set”

This is very dangerous, it can cause damage to the MFT, or other loss of data.
This will require the use CHKDSK - if this could damage the file system ...

I've had such a situation, now I prefer not to risk ..

Code: [Select]

Doubled and basic MFT different.
Correcting errors in the copy of the master file table (MFT).
Windows has made corrections to the file system.

Shane · « **Reply #7 on:** December 10, 2015, 11:32:09 pm »

Empty System Working Set isnt dangerous. Not sure why you think that. My Cleanmem tool uses it and I run it on every system all day every day.

The Windows memory manager does all the work, the Empty System Working Set api is simply the call to windows to do the job. The used memory is moved into the standby list which is still in memory and the programs have back what they use instantly, this is why it is so fast, it is still in memory. Then memory not reclaimed is left in standby for a bit by windows, then when enough time has passed the meory is free.

Windows may move a small amount to the page file, talking only a few MB, as windows sees fit. Again Windows is controlling all this.

This has nothing to do with the file system.

Shane

makinero · « **Reply #8 on:** December 11, 2015, 12:22:19 am »

Quote from: Shane on December 10, 2015, 11:32:09 pm

My Cleanmem tool uses it and I run it on every system all day every day.

Please understand that the tool MemClean is not a tool to FlushCache

I use a killer Metafile. 2 small applications and write the script BAT