Hello,
If I pickup a system with Windows 10 and use Storage Spaces (with no Resiliency), will PrimoCache accelerate the Storage Space? I am not sure if that would work or not.
Regards,
Eric
Storage Spaces - Windows 10
-
michaelduff
- Level 2
- Posts: 5
- Joined: Wed Aug 10, 2016 8:03 am
Re: Storage Spaces - Windows 10
I've been using PrimoCache with storage spaces in Windows 8, Windows 8.1 and now Windows 10, with the Storage Space upgraded to most recent format this week.
I've never had any problems and Primo does seem to cache data from this combined drive transparently with no trouble.
I think because it's a block level cache it's able to accelerate the space without concern for what the file is.
I may be fooling myself as to how much it's helping, but the Primo stats report a low but consistent cached read amount every day.
I've never had any problems and Primo does seem to cache data from this combined drive transparently with no trouble.
I think because it's a block level cache it's able to accelerate the space without concern for what the file is.
I may be fooling myself as to how much it's helping, but the Primo stats report a low but consistent cached read amount every day.
-
moltendorf
- Level 1
- Posts: 1
- Joined: Wed Aug 10, 2016 8:09 am
Re: Storage Spaces - Windows 10
I have 32G of RAM, and a 512GB Samsung 840 Pro, I have assigned 16GB of RAM L1 Cache, and 64GB of SSD L2 Cache. It definitely does help.
I have tested with all modes, no resiliency, two-way, parity, etc. WITHOUT PRIMOCACHE loading Overwatch from my 5x4TB HGST DeskStar NAS array on either ReFS or NTFS takes an eternity (initial load takes around 5-10 minutes, and once in-game most character models don't load until 3-5 minutes in, meaning invisible people shooting at invisible people and invisible me). Of course this is also somewhat impacted by BitTorrent Sync on another volume taking its own eternity indexing millions of files on boot, but even when it's done with that (usually takes around 5-6 HOURS), Overwatch still has trouble loading quickly after a cold boot (usually taking around 5 minutes + 1:15 minutes in-game), usually only warming up once Windows has all the files cached after a few matches.
WITH PRIMOCACHE and Prefetch enabled to quickly fill the L1 cache after a cold boot, the BitTorrent Sync Indexing takes around 5-10 minutes (and has NO IMPACT on the other programs since all its data is also cached in L1/L2), and Overwatch can be fired up, and in a match, with no invisible teammates or enemies within 1-2 minutes.
RAM being 500-1000 times faster than SSDs (I did the math at some point, and my conclusion was it's too damn high to remember), and SSDs being nearly 1000 times faster in IOPS than HDDs makes this difference pretty much logical.
I have tested with all modes, no resiliency, two-way, parity, etc. WITHOUT PRIMOCACHE loading Overwatch from my 5x4TB HGST DeskStar NAS array on either ReFS or NTFS takes an eternity (initial load takes around 5-10 minutes, and once in-game most character models don't load until 3-5 minutes in, meaning invisible people shooting at invisible people and invisible me). Of course this is also somewhat impacted by BitTorrent Sync on another volume taking its own eternity indexing millions of files on boot, but even when it's done with that (usually takes around 5-6 HOURS), Overwatch still has trouble loading quickly after a cold boot (usually taking around 5 minutes + 1:15 minutes in-game), usually only warming up once Windows has all the files cached after a few matches.
WITH PRIMOCACHE and Prefetch enabled to quickly fill the L1 cache after a cold boot, the BitTorrent Sync Indexing takes around 5-10 minutes (and has NO IMPACT on the other programs since all its data is also cached in L1/L2), and Overwatch can be fired up, and in a match, with no invisible teammates or enemies within 1-2 minutes.
RAM being 500-1000 times faster than SSDs (I did the math at some point, and my conclusion was it's too damn high to remember), and SSDs being nearly 1000 times faster in IOPS than HDDs makes this difference pretty much logical.
Re: Storage Spaces - Windows 10
Running mine with a 6gb L1/30gb L2 configuration on a Storage Space drive, and it seems to work fine - at least for the L1 portion. It never seems to put anything into L2, so I'm skeptical about that functionality right now. Perhaps Support will chime in and let us know..