Romex Software Forum

PrimoCache version: 2.1.0 Destop/2.1.0 Server Edition 2.0.0 Destop/2.0.0 Server Edition
Cache Settings: ssd l2 cache for read only
Windows OS: win7 and win 2008R2
Hardware Information (CPU/Motherboard/Memory/Harddisks): i7/SSD Revodrive3/Winserver2008 Corei5/ssd plextor/win764
Description: Gather Interval settings don't work

As I understand from this help cachedata can be write to L2cache when Windows is busy, but I tried all settings (Default/Idle Only/Normal(30)/Fast(10)/Fastest(1)) and cachedata was writen only when windows Idle:
1. default -about 5 sec after Idle
2. Idle only -about 5 sec after Idle too
3. Normal(30) - 30 sec after Idle
4. Fast(10) - 10 sec after Idle
5. Fast(1) - WORK GOOD!!

So cache data can't be write L2cache when Windows is busy(((

Add after 24h:
1. setting "Fast(1)" work correct!
2. It tested on ver. 2.0.0 Destop/2.0.0 Server Edition too, same results like in 2.1.0(

Does your computers always in busy state? "Gather interval" provides a way to force PrimoCache to fetch read-data into level-2 cache even when computer is busy. If this value is small, level-2 cache accumulates data fast.

Yes, my computer always (95% of time) in busy state.
1. If alot of request to read from hdd level-1 cache accumulates data good, but Level-2 is to slowly...
2. If one request to read (big file) from hhd level-2 cache accumulates data fast.

Well, for heavy busy computers, if you want to speed up the accumulation of L2 cache, you may set the Gather Interval to Fastest (1 second). By default, PrimoCache accumulates L2 cache when system is idle in order to not affect the speed of other tasks.

Best way to cache, is to copy whatever folder the info you want to cache is in.
I have actually got cache hit percentage to 100%, usually 98-99.
L2 will not cache until file is done copying.

And I thought if I had L! cache and it cached, L2 would not cache it, but L2 still caches it.
I use a small SSD for OS, A 2TB HDD, with it's first partition of 300 and a 250GB SSD caching it.
I just copy game folder before I play.
you can copy to same folder, drive, Copy triggers it as read/used and caches it.
While folder is copying L1 will cache little if at all, but soon after folder copies L2 will cache 99-100%
Also Virus scan or anything that reads the files.
For example Validating my Steam files triggers it to cache.
Setting to too fast cache can cause hiccups or really short pauses.