- Joined
- Feb 6, 2014
- Messages
- 5,112
So what would be the solution then?
More RAM, a general bit of understanding about ARC behavior, and an understanding that when you request something that isn't in the ARC buffers that it's going to be slow.
ARC works off trying to find the balance of MFU (Most Frequently Used) and MRU (Most Recently Used) data in your pool. If you've just rebooted, your ARC is empty - no data has been read off the pool yet, and nothing's been written other than maybe whatever housekeeping Windows did when it mounted the drive. When you fire up CDM and tell it to benchmark, you're firing 1GB of new writes to the pool as it builds that test file. Since ARC is empty, that 1GB of fresh new data lands in RAM, and gets to stay in ARC because it's not only the MFU (Most Frequently Used) but definitely the MRU (Most Recently Used) data. Once you actually use the pool for more than just benchmarking, the actual data set in question doesn't fit into RAM (isn't COD:Warzone something like 250GB on its own now?) so you end up missing data and having to pull from spinning disk.