Reputation: 11
I have migrated my application from Hazelcast v2.5 to v3.5 recently. With Hazelcast v2.5, my application startup time is around 20 seconds after upgrading to latest version, the time is increased to 240 seconds. That is because Hazelcast v3.5 is loading 1 or 2 keys at a time. I read the documentation, it says that 'Because of 277 partitions'.
I would like to increase my application start-up time by setting 1000 keys at a time. Is there any setting to control that in Hazelcast v3.5
Thanks, Venu
Upvotes: 1
Views: 148
Reputation: 27677
Hazelcast 3.5 loads data in chunks of 1000 by default and that's configurable with hazelcast.map.load.chunk.size
property. However, each partition loads its own set of keys and there are 271 partitions by default.
Since the number of keys you have is not large you could try decreasing the number of partitions to a lower prime number. The property is: hazelcast.partition.count
Upvotes: 3