Stick with 31G in your case. Another article on compressed Oops: https://blog.codecentric.de/en/2014/02/35gb-heap-less-32gb-java-jvm-memory-oddities/
Thomas From: Eunsu Kim [mailto:eunsu.bil...@gmail.com] Sent: Dienstag, 13. Februar 2018 08:09 To: user@cassandra.apache.org Subject: if the heap size exceeds 32GB.. 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. The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. Dynatrace Austria GmbH (registration number FN 91482h) is a company registered in Linz whose registered office is at 4040 Linz, Austria, Freist?dterstra?e 313
