Hi, Start by looking at what’s going on in the cluster when you see these long reads. Collecting a JFR record or a GC log would be nice.
Also, do you see that with concurrent reads and writes, i.e. do you have getAll and putAll executing in parallel? Perhaps there is some sort of contention between them. Finally, try to find correlation between the key sets you get high latency for. Perhaps there is something special about these keys. Stan From: Justin Ji Sent: 29 ноября 2018 г. 5:24 To: user@ignite.apache.org Subject: Re: Ignite cache.getAll takes a long time I use the default thread pool settings, can it improve the performance after I increase the system thread pool? Another question, should I add the configuration in server nodes? Looking forward to your reply -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
