Romex Software Forum

I would have expected that all reads go automatically into L2 unless L2 is filled. And if L2 is filled, a "last used first out" approach should decide which block of L2 is discarded to make space for what you are just reading. Thats the expectation. I have to think about if I can verify f...

I use this simple, very basic python script to load my cache. I run it on Python 2.7.11 in a cmd.exe window The indentation matters in python so take care to preserve that. I called it loader.py but you can call it whatever you want. First argument is the starting directory you want to cache. It wil...

PrimoCache version: 2.2 Cache Settings: 2G L1 230G L2 RW 32KB blocksize Windows OS: 7 x64 Hardware Information (CPU/Motherboard/Memory/Harddisks): haswell asus maximus vii evo 850 pro ssd Description: after running for a couple of weeks the cache seems to stop working. I noticed this on releases pr...

I've since removed PrimoCache and installed MaxVeloSSD.

Bjameson wrote:...... I'm quite sure that Romex will quickly fix any issues left.

It has been 11 months since release and nary a patch has been seen in spite of the common problems people are reporting.
While I hope you are correct I don't share your confidence that they will quickly fix anything.

Thanks for the welcome! I checked it out, and the issues reported there relate to the cache not being written to in large quantities anymore. My problem however is that the L2 cache is still written to in good amounts, but the total used size does not grow. It appears that only old data is replaced...

Any updates on this?

On my system it stops writing after it has used about 30GB of the 90GB I've allocated to L2.

Perhaps this pertains to any disk defragmentation software but I was wondering specifically about potential conflicts with primocache and perfectdisk. It seems to me that they should be able to co-exist on the same system. PD is moving files from one spot to another and primocache is caching those b...

8. Tune the level-2 cache algorithm. Changing the default value of minimum frequency at which blocks are allowed to be cached into level-2 storages. In version 0.9.8 this value is 3, now is 1. 9. Support to set the minimum frequency at which blocks are allowed to be cached into level-2 storages (CL...

minhgi wrote:Most likely the cache read is from the L1.

blocks expiring from L1 get moved to L2. Correct?
Therefore I should see L2 grow over time