There are no bad GCs in the gclog (worse is like 100ms). Everything looks great
actually from what I see. CPU utilization isn't inherently a bad thing for what
its worth.
Chris
> On Jun 14, 2018, at 1:18 PM, rajpal reddy wrote:
>
> Hey Chris,
>
> Sorry to bother you. Did you get a chance to
Hey Chris,
Sorry to bother you. Did you get a chance to look at the gclog file I sent
last night.
On Wed, Jun 13, 2018, 8:44 PM rajpal reddy wrote:
> Chris,
>
> sorry attached wrong log file. attaching gc collection seconds and cpu.
> there were going high at the same time and also attached
There are not even a 100ms GC pause in that, are you certain theres a problem?
> On Jun 13, 2018, at 3:00 PM, rajpal reddy wrote:
>
> Thanks Chris I did attached the gc logs already. reattaching them
> now.
>
> it started yesterday around 11:54PM
>> On Jun 13, 2018, at 3:56 PM, Chris Lohfink
> What is the criteria for picking up the value for G1ReservePercent?
it depends on the object allocation rate vs the size of the heap. Cassandra
ideally would be sub 500-600mb/s allocations but it can spike pretty high with
something like reading a wide partition or repair streaming which
Chris,
What is the criteria for picking up the value for G1ReservePercent?
Subroto
> On Jun 13, 2018, at 6:52 AM, Chris Lohfink wrote:
>
> G1ReservePercent
-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For
ittwoch, 13. Juni 2018 17:27
> To: user@cassandra.apache.org <mailto:user@cassandra.apache.org>
> Subject: Re: G1GC CPU Spike
>
> we have this has the Heap settings . is the HEAP_NEWSIZE is required only for
> CMS. can we get rid of that for G1GC so that it can be used?
> MAX_HEAP_
@cassandra.apache.org
Subject: Re: G1GC CPU Spike
we have this has the Heap settings . is the HEAP_NEWSIZE is required only for
CMS. can we get rid of that for G1GC so that it can be used?
MAX_HEAP_SIZE="8192M"
HEAP_NEWSIZE=“800M"
On Jun 13, 2018, at 11:15 AM, Chris Lohfink
mailto:clo
we have this has the Heap settings . is the HEAP_NEWSIZE is required only for
CMS. can we get rid of that for G1GC so that it can be used?
MAX_HEAP_SIZE="8192M"
HEAP_NEWSIZE=“800M"
> On Jun 13, 2018, at 11:15 AM, Chris Lohfink wrote:
>
> That metric is the total number of seconds spent in GC,
Chris,
We have total memory on the machine as 16G so we kept 50% to heap . initial we
had CMS we had same issues so thought of changing to G1GC we have the same
problem still
> On Jun 13, 2018, at 9:52 AM, Chris Lohfink wrote:
>
> The gc log file is best to share when asking for help with
That metric is the total number of seconds spent in GC, it will increase over
time with every young gc which is expected. Whats interesting is the rate of
growth not the fact that its increasing. If graphing tool has option to graph
derivative you should use that instead.
Chris
> On Jun 13,
jvm_gc_collection_seconds_count{gc="G1 Young Generation”} and also young
generation seconds count keep increasing
> On Jun 13, 2018, at 9:52 AM, Chris Lohfink wrote:
>
> The gc log file is best to share when asking for help with tuning. The top of
> file has all the computed args it ran
The gc log file is best to share when asking for help with tuning. The top of
file has all the computed args it ran with and it gives details on what part of
the GC is taking time. I would guess the CPU spike is from full GCs which with
that small heap of a heap is probably from evacuation
Hello,
we are using G1GC and noticing garbage collection taking a while and during
that process we are seeing cpu spiking up to 70-80%. can you please let us
know. if we have to tune any parameters for that. attaching the cassandra-env
file with jam-options.calculate_heap_sizes()
{
case
13 matches
Mail list logo
