,
0x7ff26000, 0x7ff26000)
region size 32768K, 0 young (0K), 0 survivors (0K)
Metaspace used 34162K, capacity 35315K, committed 35328K, reserved 36864K
}
[Times: user=0.67 sys=0.00, real=0.66 secs]
From: Jeff Jirsa
Date: Tuesday, February 13, 2018 at 11:40 AM
To: cassandr
> FYI, we have configured our heap for 84 GB.
>>
>> However there's more tuning that we have done beyond just the heap, so
>> make sure you are aware of what else needs to be done.
>>
>>
>>
>> *From: *"Steinmaurer, Thomas"
>> *Date
ake sure you are aware of what else needs to be done.
>
>
>
> *From: *"Steinmaurer, Thomas"
> *Date: *Tuesday, February 13, 2018 at 1:49 AM
> *To: *"user@cassandra.apache.org"
> *Subject: *RE: if the heap size exceeds 32GB..
>
>
>
> Stick with
just the heap, so make
sure you are aware of what else needs to be done.
From: "Steinmaurer, Thomas"
Date: Tuesday, February 13, 2018 at 1:49 AM
To: "user@cassandra.apache.org"
Subject: RE: if the heap size exceeds 32GB..
Stick with 31G in your case. Another articl
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 s
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, 20
