Optimal l1 cache for 8gb ram memory and 500gb hdd

[dusanka]

Hi all, i want to know what's the optimal l1 cache size for light gaming and old games for my memory and hdd, i have 8gb ddr3 1600mhz and 500gb hdd and windows 10 pro x64. Thanks.

[Support]

Please see Q9 in the following page.
http://www.romexsoftware.com/en-us/prim ... aq.html#q9

[dusanka]

Thanks. But why is my free cache too high with l1 cache 1024mb here is screenshot

[Support]

I think you may need to play the computer for a while, then L1 cache will get filled soon.

[Jaga]

It takes a while to fill the L1 cache up. You can try to force it (If it's a Steam game) by verifying the game's files. Or if you have another drive, you can copy the game folder to it (which reads it into the L1 cache as much as it can), and then delete the copy on the new drive.

With a small 1gb cache however, it's not going to cache the entire game (if it's newer) due to games being so large now. Your best bet may be to launch the game, play for 2 minutes, quit, and repeat that process half a dozen times to try and force more into the cache.

[InquiringMind]

It takes a while to fill the L1 cache up. You can try to force it (If it's a Steam game) by verifying the game's files...

Actually it shouldn't take that long at all. However the "Total Read" and "Cached Read" figures show the real cause here - there simply hasn't been much in the way of disk activity for PrimoCache to pick up on.

As Support has noted, you do need to do stuff (launch programs, etc) for the cache to fill up. The only real problem would be if something else was preventing PrimoCache from seeing disk reads at all, but with a non-zero "Total Read" figure here, that clearly isn't happening.

Verifying game files will certainly get them into the cache, but it will push the entire game in which is likely to be less ideal (unless it is a really old one less than 1GB in size). Better to let PrimoCache handle things by itself in this case.

One suggestion though - use larger block sizes. The 4KB block size here means 225MB being used for indexing - switching to a 16KB block size will quarter that and (in my experience) give better sequential read results (and, in real usage, a small "cache ahead" effect if your disk is defragmented and files sorted by path).