The Windows Dynamic Cache Service is designed to alleviate problems related to excessive cached read I/O. Microsoft does provide APIs set up to help mitigate potential issues, but with inherent limitations related especially to the lack of conflict resolution when it comes down to multiple applications, and to the absence of guidance on the configuration of the System File Cache's working set size. The SetCache utility in the Microsoft Windows Dynamic Cache Service comes to resolve this issue, and to help with the dynamical management of the Windows System File Cache size. An updated version of the Windows Dynamic Cache Service is available for download as of June 4th, 2009.

“The Microsoft Windows Dynamic Cache Service will manage the working set size of the Windows System File Cache. For 64 bit systems this service helps to address the problem of excessive cached read I/O that could eventually consume all of physical memory,” Microsoft explains in the documentation accompanying the download.

Customers should note that the service is tailored only to Windows Server 2008 and Windows Vista Service Pack 1 and earlier releases of Windows. Microsoft advised against the integration of the Windows Dynamic Cache Service with recent platforms such as Windows 7 and Windows Server 2008 R2. According to the Redmond company running the service on a newer Windows OS would most likely result in performance issues. At the same time, Microsoft warned that the service was experimental.

“Cache page churn - If the System File Cache's working set is too low and there is sustained cached read I/O, the memory manager may not be able to properly age pages. When forced to remove some pages in order to make room for new cache pages, the memory manager may inadvertently remove the wrong pages. This could result in cached page churn and decreased disk performance for all applications,” reads the Side Effects warning for the service.