Doesn’t seem to matter how much read % there is, once the cache is full, it starts to drag, and most reads are single digit range in the windows resource meter. Trouble shooting everything else before I acknowledged it was this, it just was annoying to find out my system actually gets slower in the end with the cache enabled when it gets full.
So far I’ve dropped the partition size to 23GB, until it got full it was actually fast again, no flat lines, and it seemed to be doing its job, but as it got close to the 23Gb paritition, same problem happened again, general system laginess, as if I had 3200rpm harddrives instead of 7200rpm harddrives with a cache.
Now down to 18GB, we shall see, but its not really a good option… I’ve seen people drop to 16 to claim it works there, but we didn’t pay for a 16Gb cache drive…thats for certain.
The behavior is exceptionally weird in a program like chrome canary, when the cache starts failing, the multiple tabs that I restore each time on the browser load, many just sort oif hang and take forever to load. This doesn’t happen without cache or when the cache is not full.
