Thats correct stevebsteveb wrote: ↑Fri Sep 17, 2021 10:00 am From my understanding PrimoCache works at the block level then it would use the XPRESS8K versions for example. The performance improvement will really depend on the hardware used. In some cases similar to Windows memory compression, it might be handy instead of writing it to the next tier storage. XPRESS4K from a quick test seems to improve storage only if the storage is slower than 1GB/s.
Theres a vast array hardware to consider, but as a general rule of thumb on a 4+ core system faster I/O is found with:
- Xpress16K for HDD
Xpress8K for SATA SSD
Xpress4k for NVMe SSD
Someone at MS decided: "This compression works very well! Why don't we do the same thing in RAM too!?"
So in Win 10 Superfetch/Sysmain now has 3 cache levels:
- L1: Uncompressed in RAM
L2: Compressed in RAM
L3: Compressed to Readyboost if ~random 4K -AND- Compressed to Pagefile if Sequential.
Support seems to be saying that Primocache is somehow tapping into this compression to compress the data in L1 and L2, but, as usual, does not expound on the subject!??
Maybe he's just trying to shut me up?
He's going to be a brilliant politician one day!