Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Merging of large partition versions in MVCC is inefficient #2715
If readers are short-lived relative to the time it takes to fill a memtable (likely), we will have small versions at the front and a big one at the back. Current merging in
I observed this causing large latencies in
If its related to tomek's change a simple solution is to restart the node after there are some sstables - that will guarantee the cache can not be started with continuous set.…
On Mon, Sep 25, 2017 at 10:33 PM, Piotr Jastrzębski < ***@***.***> wrote: @tgrabiec <https://github.com/tgrabiec> It can be. I don't see cache growing at all. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#2715 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADThCG5Id_yNVccYYymsKMag-m9n9ec-ks5smAAPgaJpZM4O9aEk> .