Hi Chris,
How do you map compute tasks to nodes?
Well, it's possible that 2 nodes in your cluster always stores more data
than others, that's why you face these spikes, it could happen in case of by
your affinity key, too much data could be collocated. You can check it by
using
It's hard to tell unless actual code written is known.
Although try using this JVM parameters.
-Xss256K ;; limit threadstack size
-XX:MaxGCPauseMillis=25 ;; limit max GC pause to 25ms
More tuning settings here
Greetings,
We've been running a large, high volume, low latency Ignite Compute Grid in
Production for a few months now, and, in general, things are going quite
well.
But we see a handful of large spikes a day in our application (approx. 1 per
hour)
And thus far we've been at a loss as to explain
