in order to provide "easy" multinode, we have set all of our caches to
REPLICATED and FULL_ASYNC. We get an improvment (Around 20%) with a second
node, but it is very clear that somehow the grid is waiting (95% cpu
utilization with 1 node, 75% with 2 nodes).
I understand that I should rather go for partitioned caches, but I am trying
here to provide an "easy" first step towards multinode by avoiding rewriting
I assume that these are linked to the put in the replicated caches that are
asynchronously sent to the other node.
I would like to understand a bit better these numbers and the difference
Another question: is there a way to increase the batching of messages on the
grid. Especially when it comes to replicated caches?
You are correct, these are Ignite request/response messages generated
when you are putting data into
a cache. The numbers roughly correspond to different multiples of the
number of put/putAll you are
performing. These numbers will depend on how large the objects you are
putting into the cache are, the
network throughput, cpu config, and other hardware/OS parameters.
To measure performance/fine-tune Ignite to your use case
determine the # of caches, size of objects, number of puts/gets you are
trying to perform in a given
interval. Set the cache(s) to different parameters to see what
throughput you achieve. Try using
putAll/datastreamers when possible. Use the information in the above
provided links to measure each
scenario. https://apacheignite.readme.io/docs/cache-modes Use the above provided links to measure each scenario.
Use data in this link to prepare your use case for prod: