[ https://issues.apache.org/jira/browse/IGNITE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875707#comment-15875707 ]
Taras Ledkov commented on IGNITE-3018: -------------------------------------- Waits for TC [test results|http://195.239.208.174/project.html?projectId=IgniteTests&tab=projectOverview&branch_IgniteTests=pull%2F684%2Fhead] after removing back compatibility for {{RendezvousAffinityFunction}}. > Cache affinity calculation is slow with large nodes number > ---------------------------------------------------------- > > Key: IGNITE-3018 > URL: https://issues.apache.org/jira/browse/IGNITE-3018 > Project: Ignite > Issue Type: Bug > Components: cache > Reporter: Semen Boikov > Assignee: Yakov Zhdanov > Fix For: 2.0 > > Attachments: 003.png, 064.png, 100.png, 128.png, 200.png, 300.png, > 400.png, 500.png, 600.png > > > 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). -- This message was sent by Atlassian JIRA (v6.3.15#6346)