I don't really have much to say but to try reducing/balancing on heap cache
size.
If you have a lot of objects on heap, you need to have a large heap,
obviously.
If you need to constantly add/remove on-heap objects, you'll have a lot of
work for GC.
Perhaps you can review your architecture to avoi
Hi Stan,
Thanks for your analysis.
We have increased the on heap cache size 50 and added expiry policy
[30mins].
The expiry policy is expiring the entries and the cache is never reaching to
it's max size.
But now we see high heap usage because of that GCs are happening frequently
and FULL GC
:38
To: user@ignite.apache.org
Subject: RE: High cpu on ignite server nodes
Hi Stan,
The high cpu usage is on all servers.
one doubt , what is the default expiry policy for any cache if we don't set.
Following are the stats of one cache collected from ignitevisor.
Hi Stan,
The high cpu usage is on all servers.
one doubt , what is the default expiry policy for any cache if we don't set.
Following are the stats of one cache collected from ignitevisor.
Cache 'playerSessionInfoCacheIgnite(@c18)':
+
: praveeng
Sent: 16 июня 2018 г. 17:15
To: user@ignite.apache.org
Subject: Re: High cpu on ignite server nodes
Hi ,
Following are the high cpu consumed threads.
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
36708 gmedia20 0 11.031g 6.749g 14720 R 53.5 43.5 267:15.83
Hi ,
Following are the high cpu consumed threads.
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
36708 gmedia20 0 11.031g 6.749g 14720 R 53.5 43.5 267:15.83 java
36709 gmedia20 0 11.031g 6.749g 14720 R 51.5 43.5 266:53.53 java
34433 gmedia20 0 11.03
