Romex Software Forum

Sidenote: I managed to force some Urgent writes today. I had to start a 25 gigabyte FTP download, as well as do some unzipping of large .7z archives, all on the same volume at the same time. Add to that, the volume only has a 8gb cache task for Primocache (my smallest). So yes, it's possible to get ...

Then perhaps the issue is an OS that has too much of it's memory taken by Primocache. Or it's just a memory-starved system, so Primo isn't "fitting in" well for it. That's not Primo's fault - give the system more memory perhaps?

Nope, every time I look at PrimoCache stats, Urgent writes are zero. Even if I set the cache on an abnormally long timeout like 300 seconds. I'm not using a L2 cache however, just a very large L1 cache (~32 gig) on 2 separate Cache Tasks covering three volumes on two drives. It can take a week depen...

Have you run the necessary hardware tests to ensure the underlying equipment isn't at fault? Memory tests, stress tests, disk tests, etc. I always start there if there isn't clear indication in logs.

I have no problem with the write cache modes. I've used perhaps 3 in the past, settled on 1-2, and they always did what I thought they'd do. That isn't to say I don't have ideas on other modes that might be better for other circumstances, but that's a discussion for elsewhere.

I don't have a problem with the write cache strategy either. In fact, I just did performance testing yesterday and found Intelligent to be the best that meets my needs. Worked perfectly. Your installation or test methods might be problematic, sinus.

Patiently waiting for the full 3.0. Looking forward to it.

No, you're not that old school. I still remember (and like) the flashing dot in the upper corner of the screen indicating HDD activity. I think that went back to Windows 95/98/98se. I think Sleep mode (at it's core) is problematic. Advanced tools like Primocache have a hard time becoming compatible....

I don't use Sleep mode anymore because of issues like this (not just with Primocache). It's just too problematic with many devices/drivers out there.

You can also just copy the folder(s) you want Primo to cache to another drive temporarily, then delete the new copy. That is usually enough to force the contents into the read cache.