Luca Ongaro

@tlahav 's PR definitely is a big step forward, but there are still issues remaining (see my comments on the PR). I'd recommend adding a larger base of tests, otherwise...

Hi @eksperimental , Would that return the number of writes since the last compaction? The dirt factor is calculated on the basis of the number of writes since the last...

I can add such feature in the next release, possibly under a slightly different name (maybe `CubDB.writes_since_compaction`).

Thanks for reporting @eksperimental , let me look into this. If you do have a sample project or a test to reproduce it, that’s definitely very helpful, as I have...

One thing that strikes me as odd: the database file is called `12.cub`, but the compacting file is called `15.compact`. It should be called `13.compact` instead. Are you sure it...

Never mind what I wrote above about the file name, it simply means that the previous compactions didn’t complete by the time the main process was stopped, or crashed.

Hi @eksperimental , I did not manage to reproduce this. Do you maybe have more info on how to trigger this issue? Possibly a specific sequence of actions? Thank you

I tried reproducing it with tens of thousands of concurrent writes, but no luck. On what OS and CubDB version did you experience this issue? Do you use auto compaction...

Hello @hansonkd ! Thanks a lot for your contribution. I want to take time to review it properly these days. I am already working on the option to add caching...

Not specifically for CRDTs, but for similar scenarios in embedded software where I needed to keep a queue for re-syncing when possible, I recently open-sourced [CubQ, a durable queue and...