I didn't have the dstat logs. But I think these charts is the same as dstats logs. CPU usage CPU.png <http://apache-ignite-users.70518.x6.nabble.com/file/t1346/CPU.png> Memory usage Memory.png <http://apache-ignite-users.70518.x6.nabble.com/file/t1346/Memory.png> Swap swap.png <http://apache-ignite-users.70518.x6.nabble.com/file/t1346/swap.png> Server load load.png <http://apache-ignite-users.70518.x6.nabble.com/file/t1346/load.png> Disk disk.png <http://apache-ignite-users.70518.x6.nabble.com/file/t1346/disk.png>
We're using bare metal servers for Ignite, each server has 768Gb memory and 56 core CPU. One node per server. I don't think hardware is the bottleneck here. Will enable DEBUG log help in this case? In my understanding, if JVM is in pause state Ignite can't produce any logs even DEBUG level log is enabled, right? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
