Hi, Can you actually see what the data distribution of itemid is. AffinityKey will direct Ignite to use that specific column (itemid) for partition mapping. If the data in itemid is in a narrow range, then all data will be put into fewer partitions. This might affect loading times.
more here: https://ignite.apache.org/docs/latest/data-modeling/data-partitioning https://ignite.apache.org/docs/latest/data-modeling/affinity-collocation Affinity mapping takes up more memory as various intermediate objects are created. Make sure you've allocated sufficient memory Can you collect/analyze GC logs to see whether you are running out of heap. https://apacheignite.readme.io/docs/jvm-and-system-tuning https://apacheignite.readme.io/docs/jvm-and-system-tuning#debugging-memory-usage-issues-and-gc-pauses If you are sure that enough recourses are allocated, and the system still takes a long time, add the Ignite Server log, and the GC logs here. Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
