Romex Software Forum

RobF99 wrote: ↑

Mon Jan 11, 2021 9:04 am

So the problem is with this build and Vista 32.

We tested the program on 32bit vista again for several days, but still don't reproduce the problem. Could you please send us a screenshot of your Primocache main dialog showing the cache configuration and statistics? Thanks.

1. When you click on the Cache Task on the GUI that the statistics would show cumulative data for all drives so you can get an idea how the cache is performing across the board on just one screen Thanks. This feature has been on the todo list. 2. When you click on a specific drive to also show addi...

Yes, currently PrimoCache prefetch data from underlying disks in order not to interfere L2. But we are considering to allow prefetch from L2 for better performance. Thanks.

In previous versions, CSVs were not listed and cannot be added to a cache task. Now in v4.x they are listed and you can add them to a cache task. If you try to cache CSVs in failover servers, you should set up cache with L1 cache only and should not enable Defer-Write. Otherwise data corruption migh...

If the L2 Storage volume and target volumes are on the same drive, L2 cache on target volumes will be automatically disabled because this won't help target volumes. PS. As janusz521 said, usually there is no need to use L2 on fast SSDs. L2 cache is designed to use fast drives to speed up slow drives...

janusz521 wrote: ↑

Thu Jan 14, 2021 3:23 pm

Does it mean that a L1 cache for a 4Kn drive with v3.0.2 is buggy too?

Theoretically, it should be no problem.

@dmist, Your Storage Spaces volume is a 4Kn volume. You may verify it by the command "fsutil fsinfo sectorInfo X:" where X is your Storage Spaces volume.
v3.x or prior versions doesn't check if a drive is a 4Kn volume or not, and have bugs. We will issue a new version in this month.
Thanks.

geneo wrote: ↑

Tue Jan 12, 2021 10:40 pm

Do you save L1 cache across boots? I have 4 partitions on different drives I do this for.

Do you mean "Prefetch"?

TomB wrote: ↑

Mon Jan 11, 2021 8:53 pm

For instance, does PrimoCache have to write out the entire larger cache block every time a small write occurs to one of the clusters in the block?

No, only dirty data will be written since v3.0.

We thought that many websites use "Testimonials", so tried a different phrase. yes, missed "d" and none of us noticed that before
Thank you for the correction and suggestion!