You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2017/06/02 14:13:04 UTC
[jira] [Created] (IGNITE-5398) Optimize allocations in
RendezvousAffinityFunction
Alexey Goncharuk created IGNITE-5398:
----------------------------------------
Summary: Optimize allocations in RendezvousAffinityFunction
Key: IGNITE-5398
URL: https://issues.apache.org/jira/browse/IGNITE-5398
Project: Ignite
Issue Type: Improvement
Components: cache
Affects Versions: 2.0
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
Fix For: 2.1
Currently {{RendezvousAffinityFunction}} allocates a new array of tuples (Long, ClusterNode) in order to create a sorted structure for the partition assignment. This structure is allocated for each cache and each partition, which leads to excessive GC pressure during partition map exchange.
I suggest we create a special container which is allocated once per context and reused for all partition assignments. This container can be reused efficiently for all caches because it's size is equal to the number of nodes in the assignment.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)