Lot of variables - how many reads per second per machine? - how much data per machine? - are the reads random or is there a hot working set?
Some of the suggestions online are old. CASSANDRA-8150 has some old’ish suggestions if you’re running CMS collector. Running > 16G heap should consider using G1GC and that’s tuned quite differently. Amy Tobey has a decent (2.1 era) tuning guide, I imagine The Last Pickle has one as well (and wouldn’t be surprised if Pythian and Instaclustr do too). > On Sep 5, 2019, at 7:04 AM, p...@xvalheru.org wrote: > > Hi, > > sorry to bring such question, but I want to ask what are the best JVM options > for Cassandra node? In solution I'm implementing the Cassandra serves as > read-only storage (of course populated at beginning) - the records are not > changed in time. Currently each Cassandra node's VM has this configuration > 16CPUs and 64GB of RAM. I've set these JVM options: -Xms4G and -Xmx40G; JDK > 1.8.0_221. My question is what's the best size of memory for Cassandra node > and if there's any relation between number of CPUs and memory size. When I've > searched for an answer I've found that suggested size for node is 8GB of RAM, > but I have doubts. > > Thanks > > Pat > > ---------------------------------------- > Freehosting PIPNI - http://www.pipni.cz/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org
