Fwd: Re: using zstd cause high memtable switch count

2021-02-28 Thread onmstester onmstester
No, i didn't backport that one. Thank you Sent using https://www.zoho.com/mail/ Forwarded message From: Kane Wilson To: Date: Mon, 01 Mar 2021 03:18:33 +0330 Subject: Re: using zstd cause high memtable switch count Forwarded me

Re: using zstd cause high memtable switch count

2021-02-28 Thread Kane Wilson
Did you also backport https://github.com/apache/cassandra/commit/9c1bbf3ac913f9bdf7a0e0922106804af42d2c1e to still use LZ4 for flushing? I would be curious if this is a side effect of using zstd for flushing. raft.so - Cassandra consulting, support, and managed services On Sun, Feb 28, 2021 at 9

using zstd cause high memtable switch count

2021-02-28 Thread onmstester onmstester
Hi, I'm using 3.11.2, just add the patch for zstd and changed table compression from default (LZ4) to zstd with level 1 and chunk 64kb, everything is fine (disk usage decreased by 40% and CPU usage is almost the same as before), only the memtable switch count was changed dramatically; with lz