Score:4

Windows server cluster shared volume (CSV) does not allocate full configured cache size

br flag

I have a Windows Server S2D cluster with five nodes. I have configured a 51GB CSV cache. However, after several days the server won't allocate more than about 1.5GB. I briefly saw 1.6GB. Why is the server not utilizing the available memory?

My guess is that entry time to live is quite short and instead of the cache extending the time to live to allow for the maximum utilization of the available cache size, it sticks to a fixed time span. I can think of many reasons why, such as entries that are past a certain age probably won't result in a cache hit and therefore shouldn't be cached or the resources required to manage a large cache aren't worth any supposed performance benefits. I'm really looking for a more informed explanation.

I might add that the cache hit rate is running between 5 and 55% from VM traffic.

Score:3
kz flag

CSV Cache accelerates reads only, instead of LRU or MRU algorithms it has sort of an ARC-like block retention policy (but extremely badly implemented one). Making long story short - if you don’t read the same set of the logical blocks again and again to trash some threshold values - nothing will stay within CSV cache.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.