Page 4 of 5

Re: [2019-12-31] PrimoCache 3.2.0 and 4.0.0 alpha released!

Posted: Fri Feb 14, 2020 6:21 pm
by Jaga
Axel Mertes wrote:
Fri Feb 14, 2020 12:52 pm
what is the biggest supported L2 cache size in 4.x?
We had that 2 TByte limit in the past, and now I see plenty of excessively large U.2 SSDs pop up on ebay, which would do perfectly for large scale L2 caches for very large RAID volumes. Many of those U.2 SSDs are 7.68 TByte in size, so it would be really nice, if we can utilize them in full as L2 cache for e.g. a 256 TByte volume.
I don't really have an answer Axel, but if Support indicates it is still 2TB, there are workarounds. Multiple cache tasks each can utilize their own L2 target volume, so one of the larger drives you are mentioning could be used across multiple volumes and share L2 duty for them all.

In the last year or so I've discovered a lot more usefulness in using multiple cache tasks, and don't truly mind the 2TB limitation as much as I used to. Just wanted to offer that up as a possible workaround.

Re: [2019-12-31] PrimoCache 3.2.0 and 4.0.0 alpha released!

Posted: Mon Feb 17, 2020 2:17 am
by support
Axel, sorry, it is still 2044GB in one cache task.

Re: [2019-12-31] PrimoCache 3.2.0 and 4.0.0 alpha released!

Posted: Mon Feb 24, 2020 8:12 am
by Axel Mertes
OK, then an option might be to run a set of hardware RAIDs on the lower level and stripe these on a higher level, allowing an individual SSD cache per lower level RAID set?

Lets say I have 4 * RAID6 sets with 8 * 8 TByte drives each, resulting in 4 individual volumes with ~48 TByte net size each (6 * 8 TByte net size + 2 * 8 TByte parity).
Then I assign a 2 TByte SSD cache to each of these 4 * RAID6 sets, resulting in 4 * 2 = 8 TByte total SSD cache.
I create a software stripe volume over the 4 RAID6 sets and will have a 192 TByte volume with 8 TByte SSD cache.

Do think this cascade will work?

Might I use a single 7.68 TByte U.2 SSD for this purpose and make it 4 partitions, each around 2 TByte in size?
These server models sell like 700 US$ right now on ebay. The required U.2 adapter (either a NVME to U.2 cable to PCIE to U.2 adapter) sell for like 30 US$.

Thanks for any insights.


Re: [2019-12-31] PrimoCache 3.2.0 and 4.0.0 alpha released!

Posted: Mon Feb 24, 2020 9:26 am
by support
Yes, this shall work.

Re: [2019-12-31] PrimoCache 3.2.0 and 4.0.0 alpha released!

Posted: Mon Mar 30, 2020 11:48 pm
by Logic
Feature Requests:
(assuming you want a better, faster product than the competition!?) :)

A 3rd non volatile caching tier:
Cache HDD to SATA SSD to NVME or Optane SSD.

Filtering by size and random/sequential:
Optane is fast at low que depth (QD1) random ~4K, but slower than a MP600 say at large sequential.
So cache the large sequential on MP600 and random 4K on Optane and read/write them simultaneously for an extra boost!

Simultaneous reads/writes to take advantage of drive type strengths:
If loading a game; start reading large sequential to small from the HDD (thats good at that)
and simultaneously
Small random to large from from the SSD and/or Optane Drive
and have the reads meat in the middle, or wherever they meet...

that the eBoostr guys are able to do most of what I suggest above..! Talk to them!

4: Except for your deferred write RAM cache,
you cannot compete with the speed and 'intelligence' of Windows' Prefetch and Superfetch.
All you are persisting to do is BS the idiots you don't realise they're looking at RAM speed in the Disk benching software... and that said RAM speed is MUCH slower, with less cache hits, than what Pre/Superfetch get.
So stop! You just insulting the intelligence of most users nowadays with this outdated trick that lowers the respect and ups the distrust of influential reviewers and sys admins etc!

Make Pre/superfetch controllable/settable as windblows sometime thinks switching them off for SSDs is a good idea.
Use the data they use in the prefetch etc folders to better cache hits in the L2/3 caches too..!
Hell you might even be able to set/control their retardedly set Readyboost app to do #2 and 3 above...

Add an updated version of MyDefrag (15% faster than Windows' Defrag and anything else) to the package as a means of optimising the last level of the stack to further get optimal perf from PrimoCache...
Here also, you may learn a lot about using data in the prefetch etc folder/s effectively.

Running Primocache (or its files) through
makes for some very ...'interesting' reading!!!
Why..!? Thats... really not necessary!??
Rather use that skill for the above '4: Instead' and charge more.

Re: [2019-12-31] PrimoCache 3.2.0 and 4.0.0 alpha released!

Posted: Wed Apr 01, 2020 6:33 am
by idefix44
About the PrimoCache 4.0.0a version.

Can we get informations about the PrimoCache Desktop Edition 4.0.0a?
Is it reliable?
Do you get some feedbacks from XP testers?
Which known bugs if exist?


Re: [2019-12-31] PrimoCache 3.2.0 and 4.0.0 alpha released!

Posted: Tue Apr 07, 2020 8:00 am
by support
@Logic, Thank you very much for your suggests and feature requests! We will consider them. Some features are not easy to be implemented as expected, but we will try our best to make the caching more efficient and useful.

@idefix44, so far so good. However, I'm sorry that we don't know how many testers use the XP system.

Re: [2019-12-31] PrimoCache 3.2.0 and 4.0.0 alpha released!

Posted: Wed Apr 08, 2020 1:04 am
by idefix44
I'm testing 4.0.0 since april 2020, the 5th (04/05/20).
OS: XP Home SP3 up to date.
I'll let you know if things go wrong.


Re: [2019-12-31] PrimoCache 3.2.0 and 4.0.0 alpha released!

Posted: Wed Apr 08, 2020 2:37 am
by support
Thank you, idefix44.

Re: [2019-12-31] PrimoCache 3.2.0 and 4.0.0 alpha released!

Posted: Thu Apr 09, 2020 8:55 pm
by editor0range
Hi I like the idea of storage tiering like StoreMi does it. But I was a bit sceptical about that tools future after AMD was pulling it from their servers and will be back soon with "something else"...

So I downloaded PrimoCache 3.2 and also the 4.0 alpha cause I like the idea of that "L1toL2 flush" feature. But is there a way to go even further and let the L1 and L2 cache fill at the same time when I download a game over steam for example? So after the download I can fire it up with RAM speed - if it fits my L1 cache :D - and after rebooting I still got SSD speed until it´s cached by L1 again?

Thanks for your feedback!