Microsoft Windows Dynamic Cache Service

re: Microsoft Windows Dynamic Cache Service

Dave Wade — Thu, 21 Jun 2012 10:55:19 GMT

All our X64 file servers seem to have this issue to a greater or lesser extent. It seems a total pain to make those of use who haev upgraded to the latest version jump through the hoops of opening a support to get the fix.

[The memory management algorithms in Windows 7 and Windows Server
2008 R2 operating systems were updated to address many file caching problems
found in previous versions of Windows. There are only certain unique situations
when you need to implement this service on computers that are running Windows 7
or Windows Server 2008 R2. We would like to know more about those
situations where the Dynamic Cache Service is required so we can identify areas for additional improvement. For example, the fix in KB 2564236 I/O throughput
is low when large files are read sequentially in Windows 7 or in Windows Server
2008 R2 might be more appropriate than running the Dynamic Cache Service.]

re: Microsoft Windows Dynamic Cache Service

amolssv — Fri, 13 Jan 2012 12:56:48 GMT

Hi,

I have a windows 2008 R2 EE Edition server and we are using HP Data Protector 6.2 on this server. We have 4 GB RAM on this server. Whenever backup jobs are running, the memory utilisation is 3.82 GB. If we stop the HP DP services, the memory utilisation comes down. We referred this issue to HP and they told us to follow this article.As per this article I installed the service. but when i try to start it, I get an error 1153:The specified program was written for an earlier version of windows. Can you help ? I have copied the dyncache.exe file from the retail/amd64 folder.

[At this time we do not have a publicly available version of dyncache that works on R2. If you open a support incident with Microsoft Support, they can supply you with a version of the tool that works on R2. You can find more information on opening such an incident at http://support.microsoft.com/select/Default.aspx?target=assistance.]

re: Microsoft Windows Dynamic Cache Service

Robin Ferris — Thu, 02 Sep 2010 12:36:07 GMT

i am getting this error in the applications event log when I load the service. Shoud i concerned with this?

Windows cannot open the 32-bit extensible counter DLL ASP.NET in a 64-bit environment. Contact the file vendor to obtain a 64-bit version. Alternatively, you can open the 32-bit extensible counter DLL by using the 32-bit version of Performance Monitor. To use this tool, open the Windows folder, open the Syswow64 folder, and then start Perfmon.exe

[The service uses performance counters if you enable active monitoring. It looks like you have a 32 bit only perf counter. You can ignore this error, or you can disable ASP.NET counters if you aren't using them for anything else.]

re: Microsoft Windows Dynamic Cache Service

Jay — Tue, 29 Sep 2009 23:34:37 GMT

I'm trying to mimic the setcache.exe behavior. If I set MaxSystemCacheMBytes to 4096 and MinSystemCacheMBytes would be 0 (the default which is 100MB), start the dynamic cache service and then run setcache.exe it appears that the settings have not been activated. Is this expected behavior or am I missing something?

[What operating system and processor architecture (x86 or x64) are you using? If you are on x64, make sure that you are using the 64 bit version of DynCache.exe. The minimum cache size is 100 Mbytes (unless you change the code and recompile). This is just a safety guard and I highly recommend that you do not set the minimum to below 100 Mbytes. If you are on x86, then use a number less than 4096 as the 32 bit API has this as an upper limit. Also make sure you have over 4096 Mbytes available for the cache to potentially grow into. You can use the debug build of DynCache.exe along with Debug View to collect a log of what the service doing on start up.]

re: Microsoft Windows Dynamic Cache Service

Dan — Sat, 27 Jun 2009 00:09:21 GMT

I have a SQL Server 2005 install that has 15 active instances, none of them the default one. I think this may help my issue with "There is insufficient system memory to run this query", but I would need to add the different counters for the different instances (each instance has it's own counter in the form of MSSQL$INSTANCENAME). Any recommendations on how to tackle this?

See http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/d9590d4b-6daa-4bf4-8384-06a644f3983e

[You should first verify that you are running low on physical memory when you get these errors. An error like this can be caused by numerous problems, some not even related to memory depletion. You should collect performance monitor logs and analyze the specific times of the failures. If you are running low on physical memory and most of the physical RAM is used by the cache, then this service could help you. Out of the box, you can monitor only 1 additional counter per process. If you need to monitor multiple counters, you’ll need to add additional code to the project and recompile the service.]

re: Microsoft Windows Dynamic Cache Service

LC — Mon, 20 Apr 2009 22:46:29 GMT

You mentioned above: "So that brings us back to the only provided solution - use the provided APIs."

This solution is only for 64-bit machines right? Based on your explanations above, it sounds like a 32-bit OS wouldn't suffer from this memory issue. Meaning someone could 'downgrade' their OS to 32-bit and basically escape this issue altogether right?

[Hello LC. Unfortunately 32 bit Vista/Server08 systems could experience worse problems. Prior to Vista, on 32 bit system, kernel resources were limited to certain virtual address ranges. This ended up restricting the system file cache’s working set size to a theoretical limit of about 1 GB. Since most systems have more than 1 GB of physical RAM you were generally not affected by this problem Starting with Vista, the Memory Manager can allocate kernel resources anywhere in the kernel virtual address space. This allows critical resources like paged and non-paged pool to grow larger than they previously could. Unfortunately, this change also allows the system file cache’s working set to grow and consume all of kernel virtual memory. Since the kernel virtual address space is limited to 2GB of virtual memory, the system file cache doesn’t have to consume all of physical RAM. Once it consumes all of the kernel virtual address space, allocations in critical resources like paged and non-paged pool may start failing. If these critical allocations start failing, you’ll get all kinds of generic errors from not enough system resources to access denied to application and system crashes. So for 32 bit Vista/Server 08 systems you have less virtual address range to play in. You can consume it quicker and if you do, you may end up with worse problems than a slow computer.]

re: Microsoft Windows Dynamic Cache Service

john — Wed, 08 Apr 2009 22:36:48 GMT

The folder has amd64, i386, and ia64.

Where is the folder just for 64-bit, NOT ia64 and amd64?

Where is the Windows Dynamic Cache service for 64-bit server

that is NOT IA or AMD?

thanks

[All 64 bit installs should use the amd64 bit folder. Unless you’re running an Itanium machine which uses the ia64 folder, you should use the amd64 folder.]

re: Microsoft Windows Dynamic Cache Service

ssdguy — Wed, 01 Apr 2009 21:59:35 GMT

Thanks for your answer!

Most of your recommendations are generic for most “old SSD” that have too much problems shuttering due to writes. I have not enough memory to disable the page file (only 4 GB) but I have configured the page file on another mechanical disk and I have disabled defrag and paging executive.

I know that preventing "write through" writes can be a bad idea in general and the system may end unbootable but it is like having your SO on a RAID 0. Enabling "write caching" and "advanced performance" check on disks without having a real backup power supply is also "risky" but it is not so bad if you know what you are doing.

In the end you risk the integrity of the system to gain performance... Like all of life, is about tradeoffs. I don't want you recommend that as a "best practice" but it is interesting to know how it is possible to achieve this behavior or if it is impossible on Windows.

For example it can be very useful for demo virtual machines that need to run as fast as possible and you will disregard the changes after the demo anyway.

re: Microsoft Windows Dynamic Cache Service

ssdguy — Sun, 22 Mar 2009 23:34:08 GMT

I'm experiencing system slowness due to slow writes to a SSD. I’m aware of the risks but... ¿is it possible to increase the system write cache and/or reduce the write pace of dirty pages of the cache to the disk? ¿Which is the role of the “Writewatch” on HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management (no info on Technet about it)?

I have been reading your posts about the memory management but I can’t see a way to preserve part of the cache for writes (I can set the maximum amount of memory for cache with your excellent Microsoft Windows Dynamic Cache Service and the amount of dirty pages with SystemCacheDirtyPageThreshold)

I’m using the LargeSystemCache configuration and the disk CacheIsPowerProtected and UserWriteCacheSetting options are set. All I want is to cache more writes into memory. It will be fantastic to be able to cache “write through” requests also (more risks but I can handle them)

Thanks!

[Sounds like you need Windows 7. Windows (before Windows 7) was designed to support conventional hard drives. While SSDs present themselves as conventional hard drives, there are some caveats as you are well aware of. With Windows 7 we added enhancements to improve the usage of SSDs. We will disable defrag, make larger write clusters, reduce read/write cycles, etc. These enhancements should extend SSD lifespan and improve SSD I/O performance over previous versions of Windows. The 'WriteWatch' registry key was used to watch modification of pages in physical memory. After Windows 2000, this registry key is no longer used. For current versions of Windows you should always disable disk defragmenters on SSD drives. If you have enough physical memory, you could disable paging of the Executive with the 'DisablePagingExecutive' registry key. You could even turn off the paging file to reduce write and read I/O to your drive. Please be aware, that if you turn off the paging file, you will not only be unable to collect a memory dump file, but the system could run out of available memory. I can't recommend anything that would prevent "write through" writes. If the system ever hangs, crashes or powers off unexpectedly, then you could lose critical writes (like to the registry). The system may end up being unbootable.]

re: Microsoft Windows Dynamic Cache Service

Anonymuos — Fri, 13 Mar 2009 09:19:31 GMT

Why are there folders for i386 and IA64 in the released package?

[On Windows Server 2008 x86 (32 bit) the System File Cache doesn’t have the ~1 GB theoretical limit like it did with Windows Server 2003 x86 (32 bit). The System File Cache can grow to consume nearly all of the kernel address space (2GB). The i386 (32 bit) folder is there for managing the size of the System File Cache for 32 bit servers. The IA64 folder is there for servers running on Intel IA-64 processors (not to be confused with AMD’s x64 processor that Intel has licensed).]