My default is G1GC using 50% of available RAM (so typically a minimum of 16 GB
for the JVM). That has worked in just about every case I’m familiar with. In
the old days we used CMS, but tuning that beast is a black art with few wizards
available (though several on this mailing list). Today, I
G1 is optimized for high throughput with higher pause times. It's great if
you have mixed / unpredictable workloads, and as Elliott mentioned is
mostly set & forget.
ZGC requires Java 11, which is only supported on trunk. I plan on messing
with it soon, but I haven't had time yet. We'll share
I use G1, and I think it's actually the default now for newer Cassandra
versions. For G1, I've done very little custom config/tuning. I increased
heap to 16GB (out of 64GB physical), but most of the rest is at or near
default. For the most part, it's been "feed it more RAM, and it works"
Hi Folks,
Does someone use G1 GC or ZGC on production?
Can you share your feedback, the configuration used if it's possible ?
Thanks.
Running:
SSTablemetadata /THE_KEYSPACE_DIR/mc-1421-big-Data.db
result was:
Estimated droppable tombstones: 1.2
Having STCS and data disk usage of 80% (do not have enough free space for
normal compaction), Is it OK to just: 1. stop Cassandra, 2. delete mc-1421* and
then 3. start Cassandra?
Hi, all
I'd like to know when 4.x would be released. Is there any plan this year?
--
Best regards.
Zephyr
