Hi Alexey, As I wrote in another thread, you would be able to see the CPU and heap activities there captured in JVisualVM:
http://apache-ignite-users.70518.x6.nabble.com/Puzzled-about-JVM-configuration-td7091.html The cause of it is the JVM configuration: -XX:NewSize=128m -XX:MaxNewSize=128m -XX:MaxTenuringThreshold=0 -XX:SurvivorRatio=1024 Two reasons: (1) Small young gen space size (2) Tiny survivor space with max tenuring threshold set to zero (which means no aging) As a result, a lot of minor GCs and also a large number of short-lifespan objects are promoted to old gen unnecessarily. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cannot-get-cache-through-the-REST-API-tp6806p7140.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
