Hi!
You said: "And it still uses 80%-85% of heap memory after I stop my
application", I assume you mean your client application ?
So after a GC it will still stay at 80% java heap usage ?
I assume you are using off-heap memory ?
I am not sure what the problem is, I am running an application that
updates around 10.000 cache entries every 10 seconds (persistence
enabled) and run a lot of other code that generates java heap garbage,
and the application generates around 40MB garbage per second, it fills
up the heap in a minute or so but goes down to around 20% after every gc.
How often does you application GC ? if you have 80% heap filled it
should GC pretty often I would think ?
There is garbage generated, there is not much you can do about that if
it's not your own code that generates the garbage, Ignite is not bad and
with the cache keys and values and even index of heap it should work
fine, but i guess it all depends on what your application do.
Mikael
Den 2018-11-08 kl. 14:07, skrev yangjiajun:
HI.
I have an ignite node which is version 2.6 and has fixed 12GB heap memory
and 30GB data region.I use it as a database with persistence.It uses 90%-95%
of heap memory when my application is busy(My application uses jdbc thin
connection).And it still uses 80%-85% of heap memory after I stop my
application.Ignite is in bad performance when its heap usage is high.
How to reduce ignite heap usage?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
