Hello!
https://issues.apache.org/jira/browse/IGNITE-10224 might be related. Try
closing connections every now and then. If it does not help, collect heap
dump & analyze it.
Regards,
--
Ilya Kasnacheev
пн, 12 нояб. 2018 г. в 12:44, yangjiajun <1371549...@qq.com>:
> My test scenario:
> 1.One
My test scenario:
1.One ignite node uses 12GB heap memory and 30GB off-heap memory with
persistence。Here is my cmd to start the node:
nohup ./ignite.sh ../examples/config/example-ignite.xml -J-server -J-Xms12g
-J-Xmx12g -J-XX:+AlwaysPreTouch -J-XX:+UseG1GC -J-XX:+ScavengeBeforeFullGC
Hi!
Thanks for your reply.
My client application uses jdbc thin connection to test performance of merge
into statement. We also use DPCP connection pooling providers to improve
performance.According to your suggestions and my experiment,I think idle
connections in the connection pool cause
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
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