I assume not with 4.0/4.1 though. It might be a better default than CMS, but switching a major default like this (an memtable allocation) is not something that should be snuck in at the very last moment.
In case of GC, reasonably extensive performance testing should be the expectations. Potentially revisiting some of the G1 params for the 4.1 reality - quite a lot has changed since those optional defaults where picked. > On 9 Nov 2022, at 21:13, Jeremiah D Jordan <jeremiah.jor...@gmail.com> wrote: > > At DataStax we’ve been shipping those optional G1 settings as the default for > many years now, so I am +1 to at the very least making the change in trunk, > but really I would think it fine to make it back in 4.0 and 4.1 as well.
