[2017-05-27] PrimoCache 3.0.0 Beta is available now!

[Support]

@PeterB, what's your level-1 cache size and ratio? I saw you disabled the level-2 cache for these two volumes. So their strategy depends on task's level-1 cache. If the level-1 cache is set to read-only, then the "write-only" setting for these two volumes is invalid and will be reset to "by task".

[PeterB]

@PeterB, what's your level-1 cache size and ratio? I saw you disabled the level-2 cache for these two volumes. So their strategy depends on task's level-1 cache. If the level-1 cache is set to read-only, then the "write-only" setting for these two volumes is invalid and will be reset to "by task".

Hopefully the attached image should give you most of the details you are after.

Screenshot 2017-06-04 16.47.53.png (79.43 KiB) Viewed 7261 times

Drive C is a pair of 250GB SSD's in RAID
Drive D is comprised of 4 x 128GB SSD's in RAID
I only want a write back cache for these to minimise I/O's and hopefully reduce fragmentation.
Drive E & F are both spinning drives and I want to utilise a 60GB SSD attached to run read & write cache for these.

In the old 2.7.3 I had these set as separate tasks but was hoping to combine them to reduce the overhead. Do I need to go back to this method as the system has plenty of RAM (32GB)?

[Support]

@PeterB, according to your settings, your C: and D: drives shall be able to enable "write only" strategy. We'll check if there's a bug. Could you highlight the C: drive in the main dialog instead of highlighting the task? Thus I can see the cache status for the C: drive.

Regarding using separate tasks or one combined task, it depends on if you want to dedicate cache space to certain volumes. Cache space in a task is dedicated to volumes under the task. The total overhead in these two methods is almost same.

[PeterB]

@PeterB, according to your settings, your C: and D: drives shall be able to enable "write only" strategy. We'll check if there's a bug. Could you highlight the C: drive in the main dialog instead of highlighting the task? Thus I can see the cache status for the C: drive.

Regarding using separate tasks or one combined task, it depends on if you want to dedicate cache space to certain volumes. Cache space in a task is dedicated to volumes under the task. The total overhead in these two methods is almost same.

I have attached a screenshot of the C Drive as requested. I had to rebuild the cache task to these original settings to give you an accurate reflection of the settings as I have been playing around with it a bit. Everything else seems to be working correctly and it is very stable, so credit to your team there.

C Drive.png (78.61 KiB) Viewed 7238 times

[Support]

@PeterB, thank you for the information! We'll check this bug.

[PeterB]

@PeterB, thank you for the information! We'll check this bug.

Hi support. Just letting you know that I have managed to get the customised "Volume Specification" settings to stick by manually configuring the "Individual Read/Write Cache Space" in "Advanced Level-1 Cache Options" to a manual read/write allocation. (see below)

Screenshot.png (8.71 KiB) Viewed 7188 times

Hopefully this helps.

[Daniel290881]

There is something im 3.0 beta and i am not sure if it is a bug.
I am using a lot of Excel files every day and on PrimoCache 2.7 i could see that Caching worked by watching to the Cache hit rate when opening the files. In beta 3 i cant see that anymore . Other Programms, especially exe-files work and i can see how the Cache hit rate increases. Using primo Cache 3 beta now for several days and i never saw a increasing Cache hit rate while opening the Excel files. And i am really often opening them

[Support]

@PeterB, we have addressed this problem. Thank you for the bug report!

[Support]

@Daniel290881, could you check the statistics "Total Read", "Cached Read" and "L2Storage Read"? Does "Total Read" increase when you open these excel files?

[Daniel290881]

"Total Read" doesn't increase too on this Excel files. When openig another program like an exe-file it increases (or Cached Read increases too)