1. Increasing number of partitions might improve throughput of Ignite cluster, because more partitions means less contention on cache locks. It's application dependant.
2. Affinity mapping will improve performance if puts are invoked from affinity node ( using affinityCall [1] ), because puts need not to be transferred over wire ( except for backups ). 3. If you have unexpected performance problems with Ignite, you can share you code and someone from community may give you a hint. [1] https://apacheignite.readme.io/docs/affinity-collocation#collocating-compute-with-data 2016-05-28 12:03 GMT+03:00 amitpa <[email protected]>: > Does Affinity Key imporve performance of multiple cache puts in the same > transaction? > > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Affinity-Key-Mapping-tp5212p5290.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Best regards, Alexei Scherbakov
