Option 1 is not usually good, because large heaps are likely to cause long GC
pauses. You should either start several smaller nodes, or use off-heap
memory [1].

As for query performance, there is a chance that you can improve *latency*
by starting several nodes (generally, as many nodes as many cores you have).
This is especially effective if queries imply large scans (e.g. aggregation
of the whole table, or other analytical use cases) and if the number of
parallel queries is not too big. However, if your system is highly loaded,
there are a lot of concurrent small queries and you're more interested in
throughput, this is not going to make much difference.

[1] https://apacheignite.readme.io/docs/off-heap-memory

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Performance-of-multiple-ignite-JVMs-within-single-node-tp9753p9758.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Reply via email to