Here is a useful guide on tuning Cassandra heap https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsTuneJVM.html#opsTuneJVM__tuning-the-java-heap .
TL;DR You wouldn't want to allocate more than 1/2 of physical memory to heap so you wouldn't exceed 32 GB anyway. On Mon, Feb 12, 2018 at 11:08 PM, Eunsu Kim <eunsu.bil...@gmail.com> wrote: > https://www.elastic.co/guide/en/elasticsearch/guide/ > current/heap-sizing.html#compressed_oops > > According to the article above, if the heap size of the JVM is about 32GB, > it is a waste of memory because it can not use the compress object pointer. > (Of course talking about ES) > > But if this is a general theory about the JVM, does that apply to > Cassandra as well? > > I am using a 64 GB physical memory server and I am concerned about heap > size allocation. > > Thank you. > -- Ben Wood Software Engineer - Data Agility Mesosphere
