Romex Software Forum

PrimoCache 3.0.3 request.

Can we hope an option allowing to cache the written blocks (after being written on the underlying volume) as the read blocks are (same gather interval setting)?

Thanks.

@idefix44, do you mean to cache write-data? If I understand your question correctly, when you set up write cache space or shared cache space in L1/L2 advanced settings, PrimoCache will also cache write-data.

@support, sorry, but I don't understand that you don't understand what I mean...

The purpose is to cache read and written datas (not datas to write).
L2 isn't used like an L1 expansion (caching datas to write when Defer-Write is enabled).

L2 stores Read and Written datas with the same gather interval setting.

Now I understand. So you're talking about L2 cache, right? When you set up write cache space or shared cache space in L1/L2 advanced settings, PrimoCache will also cache write-data whether Defer-Write is enabled or not. If Defer-Write is not enabled, incoming write-data will be stored to L1/L2 cache and target disk at same time. If Defer-Write is enabled, incoming write-data will be stored to L1/L2 cache and later written to target disk.
I understand that you want L2 to gather write-data just as it gathers read-data. I'm not sure if this will be supported or not. But I think above method is a workaround for this request?

I understand that you want L2 to gather write-data just as it gathers read-data. It's what I mean.

PrimoCahce allow caching of network mapped drives?
It would be very useful for us.
Thanks!

@rolandi350, sorry but no.

And sometime in the future?
Or alternative solution?

Primocache is a block-level caching program. What you're referring to is a file-level caching program... apples to oranges.

The only solution using Primocache is to get and install another copy on the system hosting the network file shares, so that they can be cached there and delivered more quickly.

There are a lot of problems trying to cache network files - the biggest is knowing when the target machine on the network has changed the file you're trying to cache. You simply can't, unless you put a realtime tracker on the file, which then impacts network and host performance. It's just not practical in that sense.

Seasonal version release question? =)

Was wondering if we will be able to test some of the new features during seasonal holidays.