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 avoid having on-heap caching whatsoever to minimize the impact of Java GC. Stan -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
