Too Much Cache?

Too Much Cache?

  • Comments 31

Cache is used to reduce the performance impact when accessing data that resides on slower storage media.  Without it your PC would crawl along and become nearly unusable.  If data or code pages for a file reside on the hard disk, it can take the system 10 milliseconds to access the page.  If that same page resides in physical RAM, it can take the system 10 nanoseconds to access the page.  Access to physical RAM is about 1 million times faster than to a hard drive.  It would be great if we could load up all the contents of the hard drive into RAM, but that scenario is cost prohibitive and dangerous.  Hard disk space is far less costly and is non-volatile (the data is persistent even when disconnected from a power source). 


Since we are limited with how much RAM we can stick in a box, we have to make the most of it.  We have to share this crucial physical resource with all running processes, the kernel and the file system cache.  You can read more about how this works here:


The file system cache resides in kernel address space.  It is used to buffer access to the much slower hard drive.  The file system cache will map and unmap sections of files based on access patterns, application requests and I/O demand.  The file system cache operates like a process working set.  You can monitor the size of your file system cache's working set using the Memory\System Cache Resident Bytes performance monitor counter.  This value will only show you the system cache's current working set.  Once a page is removed from the cache's working set it is placed on the standby list.  You should consider the standby pages from the cache manager as a part of your file cache.  You can also consider these standby pages to be available pages.  This is what the pre-Vista Task Manager does.  Most of what you see as available pages is probably standby pages for the system cache.  Once again, you can read more about this in "The Memory Shell Game" post.


Too Much Cache is a Bad Thing

The memory manager works on a demand based algorithm.  Physical pages are given to where the current demand is.  If the demand isn't satisfied, the memory manager will start pulling pages from other areas, scrub them and send them to help meet the growing demand.  Just like any process, the system file cache can consume physical memory if there is sufficient demand. 

Having a lot of cache is generally not a bad thing, but if it is at the expense of other processes it can be detrimental to system performance.  There are two different ways this can occur - read and write I/O.


Excessive Cached Write I/O

Applications and services can dump lots of write I/O to files through the system file cache.  The system cache's working set will grow as it buffers this write I/O.  System threads will start flushing these dirty pages to disk.  Typically the disk can't keep up with the I/O speed of an application, so the writes get buffered into the system cache.  At a certain point the cache manager will reach a dirty page threshold and start to throttle I/O into the cache manager.  It does this to prevent applications from overtaking physical RAM with write I/O.  There are however, some isolated scenarios where this throttle doesn't work as well as we would expect.  This could be due to bad applications or drivers or not having enough memory.  Fortunately, we can tune the amount of dirty pages allowed before the system starts throttling cached write I/O.  This is handled by the SystemCacheDirtyPageThreshold registry value as described in Knowledge Base article 920739:;EN-US;920739


Excessive Cached Read I/O

While the SystemCacheDirtyPageThreshold registry value can tune the number of write/dirty pages in physical memory, it does not affect the number of read pages in the system cache.  If an application or driver opens many files and actively reads from them continuously through the cache manager, then the memory manger will move more physical pages to the cache manager.  If this demand continues to grow, the cache manager can grow to consume physical memory and other process (with less memory demand) will get paged out to disk.  This read I/O demand may be legitimate or may be due to poor application scalability.  The memory manager doesn't know if the demand is due to bad behavior or not, so pages are moved simply because there is demand for it.  On a 32 bit system, the file system cache working set is essentially limited to 1 GB.  This is the maximum size that we blocked off in the kernel for the system cache working set.  Since most systems have more than 1 GB of physical RAM today, having the system cache working set consume physical RAM with read I/O is less likely. 

This scenario; however, is more prevalent on 64 bit systems.  With the increase in pointer length, the kernel's address space is greatly expanded.  The system cache's working set limit can and typically does exceed how much memory is installed in the system.  It is much easier for applications and drivers to load up the system cache with read I/O.  If the demand is sustained, the system cache's working set can grow to consume physical memory.  This will push out other process and kernel resources out to the page file and can be very detrimental to system performance.

Fortunately we can also tune the server for this scenario.  We have added two APIs to query and set the system file cache size - GetSystemFileCacheSize() and SetSystemFileCacheSize().  We chose to implement this tuning option via API calls to allow setting the cache working set size dynamically.  I’ve uploaded the source code and compiled binaries for a sample application that calls these APIs.  The source code can be compiled using the Windows DDK, or you can use the included binaries.  The 32 bit version is limited to setting the cache working set to a maximum of 4 GB.  The 64 bit version does not have this limitation.  The sample code and included binaries are completely unsupported.  It is just a quick and dirty implementation with little error handling.

Leave a Comment
  • Please add 2 and 8 and type the answer here:
  • Post
  • Tool works fine on 2008 x64 in that it commits the change immediately after running the command. However the setting doesn't stick after a server reboot but defaults back to 8386607MB. Is there a way to make the setting permanent or do we have to resolve to running the tool during the Windows startup sequence?

    [Good question. SetCache has been replaced by the Microsoft Windows Dynamic Cache Service. You read more about it here. These settings are not persistent and will revert to default values when the system starts. You can either use SetCache in a local system startup script or use the Microsoft Windows Dynamic Cache Service. The new service will auto-start with the system and set the cache limit based on many configurable options.]
  • Thank you very much for your post. I am so sory not found it 2 years ago... I am trying to donload binaries with no success. Tried several ISP's. Please, help?

  • CecoM, this has now been replaced with Microsoft Windows Dynamic Cache Service - grab it from

  • I just tried to install this tool on Windows 2008 R2 but it failed to start with the notification that the tool was written for an earlier version of Windows.

    Will there be an update soon or is there a tool provided within R2 that manages the cache size?

    [ Thanks for the great question! The SetCache tool is not an installable tool. Additionally it has been replaced by the Microsoft Windows Dynamic Cache Service. Either way, these tools help to mitigate the problem of excessive growth of the system file cache on versions of Windows prior to Windows 7 and Windows Server 2008 R2. We have updated the memory manager algorithms in Windows 7 and Windows Server 2008 R2 to address this issue natively in the Operating System. You should not use these tools on the latest version of Windows. ]
  • I wanted to get some clarification after reading the post related to the Windows Dynamic Cache Service. I am running windows 2008 R2 NFS server. Our workload performs heavy I/O operations to large files. We are running out of memory during peak workloads. You (Team) Mentioned that some architectural changes to memory management in R2 may address these issues Will this service help my situation? does it even apply to R2? If so your help and guidance would be appreciated as i truly believe this to be our issue! P.S - I need your help bad if im going to solidify Windows continued use for our application...please help!

    (Question from another blog reader) I am seeing similar issues on Windows 7. What should I do to try to address/investigate such an issue since they are not supposed to exist anymore?

    [ Windows 7 and 2008 R2 has several Memory Manager changes that should help mitigate this problem. That being said, don't expect that the cache won't utilize a fair share of physical RAM if there is a lot of demand for cached I/O. It may use quite a bit of physical RAM, but not at the expense of other processes and it shouldn't completely deplete available memory. Some process working set trimming may occur, but that comes from really old pages that should be repurposed. The other thing to keep in mind is that under R2 you may not be experiencing a cache consumption problem, but an I/O bottleneck. If your disks are saturated with normal priority I/O, the rest of the system will operate slowly as the I/O will contend with the cached reads and writes. You need to carefully analyze the perfmon logs from this scenario in order to determine what is going on. Please contact Microsoft Support if you need assistance in reviewing the perfmon logs. ]
    Hello, We recently updated from Windows 2008 to 2008 R2 and we see different system cache behavior. We have a memory intensive application which is running on a dedicated server by its own. 2008 R2 does not let it use up the entire RAM of the server, it limits the system cache to around 50% of total physical memory. This creates a big problem for us because we are using iSCSI and the data used to fill up the system cache entirely with the previous version of Windows, and it doesn't happen any more with R2. We've tried using the SetSystemFileCacheSize API but it doesn't seem to have any effect whatsoever to increase the maximum cache size. This is pretty important for us, so any help would be hugely appreciated. Thank you, Andrei Alecu
    [ Other than the size of the System File Cache's working set, are you seeing a performance difference between 2008 and 2008 R2? When you say that you have a memory intensive application, are you referring to your process' working set? If so then using the APIs won't affect your process' working set. The APIs are only used to set limits on the System File Cache's working set. Also note, that you are just looking at the size of the working set for the System File Cache. Pages that are removed from the working set are placed on the standby list and can be easily soft faulted back into the working set. If you are moving a lot of pages through the cache, chances are that your standby list will be mostly full of cached pages. The "Cache" isn't limited to the size of its working set. ]
    "Could not start DynCache service on Local Computer. Error 216 (0xd8)" This is on a a Windows Server 2003 R2 Enterprise x64 box at SP2.
    [ You can use the debug build (included) and Debug View to see exactly why the service is exiting. Also make sure that you are using the AMD 64 bit version of the executable. ]
    I have IA64 server with Windows 2003 DC edition and Oracle is running. is it a better idea to use Microsoft Windows Dynamic Cache Service in my enviornment?
    [ If you have applications that perform a lot of cache read I/O, you can benefit from this service. This would include applications that backup the Oracle database using file copies rather than Oracle interfaces. You can also benefit from this service is your admins could be copying large or many files off of the server. ]
    We are having the page out issue when copying a large backup between to servers. Both are W2k8 x64 with SQL 2k8. One has 2 instances and the other is a cluster. The copy is from the cluster, using a SAN, to the other machine. To top it off, a virus scan is running on both servers, but it is configured to exclude the recommeded SQL files. The error occurs on both servers. If it turns out the cache is responsible, how should it be addressed? Seems like I have two issues. One, can the service watches two instances. The other, is the service okay on a cluster? Any advice? Will there be a hotfix that addresses this? Thanks.
    [ You need to use Perfmon to monitor Available Memory and the size of the system file cache. If during your test, you see the system file cache grows to overtake all of physical RAM, then you should use this service. The service only works on one server. You need to install and configure it on each of your servers. This service will work on clustered servers. There will be no hotfix for this issue. If your cache is consuming physical RAM, you need to use the provided APIs. If you want to save time and do not want to write your own solution, you can use the Dynamic Cache Service to help mitigate this problem. ]
    Hello, On windows 7 X64 i notice that when a large file is passed through the "write cache" the file gets loaded into memory completely. This becomes a problem with files larger than the available ram number (the system becomes sluggish) Is there any way to limit the maximum cache size on windows 7 to prevent the write cache from taking up all available ram?
    [ You can use the GetSystemFileCacheSize() and SetSystemFileCacheSize() APIs on Windows 7 to limit the size of the System File Cache’s working set. The Dynamic Cache Service is one example of how to use these APIs, but there is a hard coded check for Windows 7 in the service. If you absolutely must use this service on Windows 7, you need to modify the code to remove the check. Then the service can work on Windows 7/2008 R2. Before you do this, you really should review a perfmon log of the problem. Do not rely on Task Manager for this problem. The cache may consume a lot of physical RAM, but it should not completely consume it. Some working set trimming may occur, but that is from really old pages that need to be repurposed. Before taking drastic measures, you need to verify that you do have a caching problem and not a disk I/O bandwidth problem. ]
    I am using Vista Ultimate 64-bit on a Q6600 CPU with 8GB of RAM installed. I have added the amd64 version of DynCache.exe to my system and created the service and registry entries. I have set: MaxSystemCacheMBytes = 2048 and it is making no difference. If I copy a large file from a network drive, Task Manager reports the entire available amount of Free memory disappears and the Cached counter climbs to the limit. How can I limit this? Please tell me there is a way. After copying a file like this, the system is so slow to do anything else. As an aside, has this issue been fixed in Win7 and if so, how is it configured? Same registry entries? Thanks to anyone who can help! -Michael
    [ Don’t use Task Manager to troubleshoot this problem. Task Manager combines standby pages and the system file cache’s working set together and reports it as Cached Pages. Standby Pages are like cached pages in that they can be quickly soft-faulted back into the process’ working set, so this reporting is accurate. They are also like available memory because they can be quickly zeroed and given to another process. You should use Perfmon to see what the actual size of the system file cache is. If it is still exceeding the limit you set, use the included debug version and Debug View to see what the service is really doing. This issue has been greatly mitigated in Windows 7. We cannot backport the changes to Vista. For pre-Windows 7 operating systems, you need to use the provided APIs. The Dynamic Cache Service is an example of a solution using the provided APIs. ]
    I thank you for this post. Accidentially even the Microsoft Windows Dynamic Cache Service seems to solve my problem. I tried different settings whitout success. When I copy large files ~ 10GB from a quick disk to a slow disk (e.g. from 12-disk-raid to single SATA-Disk, or USB external disk), my system stalls for a while, most running applications do not respond any more. When I open taskmanager, I can see, that the amount of free ram goes to zero within seconds, then the problems begin. Probably this are even standby-pages, but why does this cause such behaviour? I found at microsoft a hotfix (920739) for Server2k3, which describes exactly my problem but I use server2k8, and this won´t fit. Don’t use Task Manager to look at your memory counters. Task Manager is good for a quick reference, but not good for troubleshooting a specific scenario. Also, don’t rely solely on Free Pages. Your system could have available pages on the standby list. These pages can be easily converted to free, then zeroed then given to another process. You should use Perfmon to view your memory counters. Check out this post for more information:
    [Please don’t use Task Manager to look at your memory counters. Task Manager is good for a quick reference, but not good for troubleshooting a specific scenario. Also, don’t rely solely on Free Pages. Your system could have available pages on the standby list. These pages can be easily converted to free, then zeroed then given to another process. You should use Perfmon to view your memory counters. Check out this post for more information: Also, if you think that the Dynamic Cache Service is not working, you can use the debug build and DebugView to see exactly what it is doing. . ]
  • I'm a SQL Server Analysis Services MVP, and I'm very interested in the interaction between the system file cache and SSAS (as it leverages the system file cache heavily). Do you know any experts on that topic from Microsoft that I should ping? Two quick questions for you. I've written some C# code that lets you clear the windows system file cache. The main reason for this is to repeatably retest the performance of an Analysis Services query on a completely cold system file cache (without server reboot). Two questions: 1. Is uses NtSetSystemInformation. Is this doing anything different than SetSystemFileCacheSize? You can see the code here: 2. From your article, it appears that limiting the system file cache doesn't zero the system file cache memory that's trimmed, but rather moves it to standby. Is there an API (or any other way) of clearing standby memory in the system file cache? That code mentioned above isn't producing repeatable cold system file cache tests, and I believe it's because soft faults from standby are so much faster than hard faults.

    [SetSystemFileCacheSize() internally uses NtSetSystemInformation().  I would recommend using SetSystemFileCacheSize() over NtSetSystemInformation() because SetSystemFileCacheSize() is a public API.  While you can use NtSetSystemInformation(), you run a greater risk of your application breaking if we change the interface.

    If you want to clear out physical RAM without a server reboot, I would recommend creating an application that will consume most of available memory and then dump the pages onto the free list.  First get the current File System Cache’s working set size, then set the limit to something fairly low (but not too low).  Next find out how much available memory is on the system, and then allocate that much memory in your process (leave about 64 MBs free).  Write at least one byte per page to guarantee that it will be committed to your process’s working set.  Finally restore the System File Cache’s work set to where it was and then exit the process.]

  • I'm not able to start the DynCache service on my Windows Server 2008 SP2 64-bit. Struggling with these for some time now. Please help!!!




    Windows could not start the Dynamic Cache Service service on Local Computer.

    Error 216: 0xd8




  • On Windows 7 SP1 I had to hardcode into the LimitCache function:



    and it now works:) (upper limit is 512MBytes, as reported by SysInternals CacheSet, and once it reached this limit, it didn't cross it).

  • Hello, very interesting article.

    I am using Windows Server 2008 R2 and am seeing this runaway file cache issue consuming all of the available physical RAM.

    My application does a ton of random access reads and writes.

    What were the changes to the memory manager between Windows 2008 and 2008 R2?

    I am curious since the runaway cache problem is still there.

    What is your recommendation for dealing with it on Windows 2008 R2?

    [The cache manager in Windows Server 2008 R2 handles almost all scenarios more efficiently, and usually avoids the need for dyncache.  Unless you have many individual files open, the cache manager should not encounter the scenario described in this article on R2.  It is difficult to provide 1:1 support through blog comments, if you need troubleshooting assistance you may want to open a support incident so that our engineers can assist you.]

  • Ugh, this is terribad. With the current Steam sale lots of downloading is being done. While Steam is downloading 'Cache WS' in Process Explorer is constantly growing. I saw 3GB Cache WS on the 4GB system and instead of discarding this clearly useless memory, it's starting to swap running programs to disk, aarrgh. It's currently so bad I just run Cacheset.exe 1024 1024 half-hourly. Not that it would be stick to anywhere near 1024KB but at least it clears the cache instantly.

    [You may benefit from the service described in this article:]

  • Is SystemCacheDirtyPageThreshold still relevant for Windows Server 2012?


    [That setting is only relevant on Windows Server 2003 SP2, or SP1 with KB920739 installed.  For more information refer to]

  • On one of your posts I see the below response-

    { Thanks for the great question! The SetCache tool is not an installable tool. Additionally it has been replaced by the Microsoft Windows Dynamic Cache Service. Either way, these tools help to mitigate the problem of excessive growth of the system file cache on versions of Windows prior to Windows 7 and Windows Server 2008 R2. We have updated the memory manager algorithms in Windows 7 and Windows Server 2008 R2 to address this issue natively in the Operating System. You should not use these tools on the latest version of Windows. ]

    However I am experiencing the MetaFile utilizing over 90% of my RAM on Windows Server 2008 R2 w/ SP1 that has 16GB of RAM, should I install the Windows Dynamic Cache Services? -

    I also question this as the ReadMe file included the the Dynamic Cache Service zip states the below -

    This service will only run on Windows Server 2008 R2 or earlier versions of Windows.  Do not attempt to run this service on a version of Windows after Windows Server 2008 R2 as it will most likely cause performance problems.

    [Please refer to this article for information on dyncache:]

  • I'm trying to run this service on Windows Server 2008 R2 (64 bit) but have been unable to make it work. Should I use the the Dyncache.exe under the I386 folder or the one under AMD64? If I use the 64 bit one, should that go under the C:\Windows\SysWOW64 or should it be under the System32 folder?

    [The answer to your question depends on which 64-bit version of Windows you are using.  If you are using x64, then use the version in the amd64 folder and put it in the system32 folder.  Note that AMD64 refers to the 64-bit extended x86 architecture, and is not specific to hardware manufactured by AMD.  If you are using the Itanium version of Windows, use the version in the ia64 folder and put it in system32.]

  • The link to the source code seems to be dead.

    [This tool is obsolete and was replaced by dyncache.  The source for dyncache is included in the download package.]

  • What it means:

    The system clock varies too much (v=662.91)

    [This text does not appear in the article, unfortunately we do not know what it means either.]

Page 2 of 3 (31 items) 123