In order to tune GC, you need gc.log or jvm metrics, you can check on https://gceasy.io/ and see the results before and after the change.
On Mon, Jul 19, 2021 at 7:21 PM Luca Rondanini <luca.rondan...@gmail.com> wrote: > Thanks Yakir, > > I can already experience slow repairs and startups but I'd like to > stabilize the system before jumping into refactoring (columns are not a > problem, max 10/cols per table). Do you believe it's a GC problem to cause > the timeouts and crashes? I'll give it a try and update this post. > > Thanks, > Luca > > > > On Mon, Jul 19, 2021 at 9:14 AM Yakir Gibraltar <yaki...@gmail.com> wrote: > >> I recommend rethinking about this design, hard to maintain, slow startup >> and repair . >> About GC, try to replace CMS with G1 , see doc : >> https://docs.datastax.com/en/dse/6.0/dse-admin/datastax_enterprise/operations/opsTuningGcAbout.html >> BTW, also many columns may affect performance, see doc: >> https://thelastpickle.com/blog/2020/12/17/impacts-of-many-columns-in-cassandra-table.html >> >> Cheers, Yakir Gibraltar >> >> -- *בברכה,* *יקיר גיברלטר*
