Thank you Sean and Rahul for the consult
On Sun, Jul 29, 2018 at 6:52 PM, Rahul Singh
wrote:
> Depends on which GC you are using but you can definitely manage GC - but
> you will always be stuck to the upper limit of memory.
>
> I found the Hubspot gc visualizer and the associated blog post
Depends on which GC you are using but you can definitely manage GC - but you
will always be stuck to the upper limit of memory.
I found the Hubspot gc visualizer and the associated blog post very helpful in
the past.
https://github.com/HubSpot/gc_log_visualizer/blob/master/README.md
@cassandra.apache.org
Subject: RE: [EXTERNAL] optimization to cassandra-env.sh
Check the archives for CMS or G1 (whichever garbage collector you are using).
There has been significant and good advice on both. In general, though, G1 has
one basic number to set and does very well in our use cases. CMS has lots
: R1 J1
Sent: Thursday, July 26, 2018 1:28 PM
To: user@cassandra.apache.org
Subject: [EXTERNAL] optimization to cassandra-env.sh
Any one has tried to optimize or change cassandra-env.sh in an server
installation to make it use more heap size for garbage collection ?
Any ideas ? We are having some
Any one has tried to optimize or change cassandra-env.sh in an server
installation to make it use more heap size for garbage collection ?
Any ideas ? We are having some oom issues and thinking if we have options
other than increasing RAM for that node.
Regards
