Romex Software Forum

Given SSD's have 300-500MB/s write speed and HDD's 150MB/s, it's very much the reverse. Populating L2 at full speed would certainly bottleneck the HDD until L2 was filled. It should populate L2 at the same speed that the HDD is read by the user software, essentially, it should do something like thi...

I think that the problem is in the L2 algorithm. While L1 is written immediately after reading the requested block, L2 is written some time after reading (and requires a second read). Essentially, if I could trick PrimoCache into thinking that my SSD is actually RAM, it would work perfectly.

L1 for me fills up as soon as the data is read. If I read a 7GB file from a disk, the free space in L1 shrinks by 7GB. However, I need more cache (and it does not need to be very fast, just lower latency than a hard drive) and RAM is expensive, so I would rather use a SSD. However, the L2 cache stra...

That's interesting - so it writes to L1 cache all the time (does not matter whether source disk is busy or not), but only writes to L2 if source disk is idle. Would having some L1 cache speed up the filling of L2 (because I would expect it to write to L2 from L1). I added 8GB of L1 cache to see how ...

Hello, I am trying the trial version of PrimoCache 1.0.1 and initially I set it to use RAM only - that worked perfectly. Now I borrowed an SSD to test whether I should buy one. I created a single partition on it (55GB) and set it as L2 cache. At first i seemed OK, but then Primocache stopped writing...