Description
With large number of cache server nodes (> 200) RendezvousAffinityFunction and FairAffinityFunction work pretty slow .
For RendezvousAffinityFunction.assignPartitions can take hundredes of milliseconds, for FairAffinityFunction it can take seconds.
For RendezvousAffinityFunction most time is spent in MD5 hash calculation and nodes list sorting. As optimization we can try to cache
{partion, node}MD5 hash or try another hash function. Also several minor optimizations are possible (avoid unncecessary allocations, only one thread local 'get', etc).
Attachments
Attachments
Issue Links
- causes
-
IGNITE-12896 excludeNeighbors=true breaks zone-awareness
- Open
- is duplicated by
-
IGNITE-3905 Optimize RendezvousAffinityFunction
- Resolved
- is related to
-
IGNITE-4765 Different partition mapping for caches that use Fair Affinity Function
- Closed
- relates to
-
IGNITE-4756 Print info about partition distribution to log
- Resolved
- links to