Romex Software Forum

L2 cache works basically with LRU algorithm. Basically - when filling up, all reads from HDD are 'copied' to L2. When L2 is full, data that is used last (or not used) is replaced with new data that is used. 64GB cache is generally enough for several games. However, copying lots of stuff around on dr...

Another thing to keep in mind - L1 uses fixed amount of memory. That memory, if not used for L1 is still used by Windows for filesystem cache. As Jaga said, in your case I'd also suggest to not use L1, or use only small amount (such as 1GB), and rest is read thru L2. This will be good enough :) Howe...

This was one of my goals with this suggestion too: copying (populating) data from L1 to L2 should have minor/no impact on normal I/O, since L2 is much faster than HDD which is accelerated. With option to copy directly from L1 to L2 you remove need for another read from HDD to fill up L2. On busy sys...

If Gather Interval is set to '1' (aka, immediate) for L2, it still only works after HDD is IDLE for minimum amount of time. The problem: Example 1: cache is set for read-only L1 is set to 2GB L2 is set to 60GB If I start reading file which is 8GB in size, it will start filling L1 cache, and start ov...

For test, I set up L2 cache of size only 1GB. Then I read file which is 10G in size. After that, PrimoCache starts filling up L2 cache - by reading from source drive&writing to L2 whole 10G - instead only 1G! Basically, you are overwriting (several times) older data on L2 on drive, instead to ca...

Would it be possible to allow caching with multiboot? More specifically, scenario when it could/should work: Two OS's, each has installed primocache. Each has same L2 device and same target devices for caching. This should be possible by using UUID's of devices, so same devices are checked&used ...