best settings for gaming?
best settings for gaming?
so i got primocache a while back because it was well recommended but having a hard time fully setting it up. i was wondering if their was a good guide somewhere that i cant find for this? mostly want to have fast download for updating games and and ok launch times for the couple i am currently playing. i have a samsung 970 2tb nvme ssd, 8tb seagate ST8000DM004, 128gb of ddr5 ram. any suggestions?
Last edited by orkid1989 on Fri Jan 10, 2025 7:48 pm, edited 1 time in total.
Re: best settings for gaming?
this is how I use it for a iSCSI volume for my STEAM library, hosted on a NAS (TrueNAS CORE)
- Attachments
-
- Screenshot 2025-01-12 023835.png (301.9 KiB) Viewed 8986 times
Re: best settings for gaming?
I think most original settings are good. However, you can change the cache block size to 32KB or 64KB. This will reduce the memory overhead. Currently is about 17GB which is a waste. The memory was used as memory overhead can be assigned to L1 cache, thus you can change the L1 cache size to 40GB or more.
You can also reduce L2 write cache space. This may be too large in your current settings since you only set up 60s latency. I think 200GB Write space is enough because you also have 32GB L1 cache for Defer-Write. The remaining SSD space can be used as L2 read cache space.
Please note that above L1/L2 size settings are just for your reference, you can tune them according to the cache statistics. For more information, please see https://www.romexsoftware.com/en-us/pri ... write.html
Also please note that after you change the block size or L2 cache space, current L2 cache content will be cleared and PrimoCache will have to repopulate L2 read cache.
You can also reduce L2 write cache space. This may be too large in your current settings since you only set up 60s latency. I think 200GB Write space is enough because you also have 32GB L1 cache for Defer-Write. The remaining SSD space can be used as L2 read cache space.
Please note that above L1/L2 size settings are just for your reference, you can tune them according to the cache statistics. For more information, please see https://www.romexsoftware.com/en-us/pri ... write.html
Also please note that after you change the block size or L2 cache space, current L2 cache content will be cleared and PrimoCache will have to repopulate L2 read cache.