You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Michael Smith (Jira)" <ji...@apache.org> on 2022/05/26 20:57:00 UTC

[jira] [Closed] (IMPALA-9221) Optimize HashRing's map implementation

     [ https://issues.apache.org/jira/browse/IMPALA-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Smith closed IMPALA-9221.
---------------------------------
    Resolution: Won't Fix

> Optimize HashRing's map implementation
> --------------------------------------
>
>                 Key: IMPALA-9221
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9221
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>    Affects Versions: Impala 3.4.0
>            Reporter: Joe McDonnell
>            Assignee: Michael Smith
>            Priority: Major
>         Attachments: image-2022-05-26-10-23-57-678.png, image-2022-05-26-13-54-15-448.png, image-2022-05-26-13-54-31-752.png
>
>
> The hash ring used for consistent scheduling currently uses a std::map for the hash-to-IpAddr lookup. HashRing is heavy on reads, with writes only happening when executors come and go. There are some cases where we copy the HashRing.
> The standard map uses a large number of small allocations. This hurts cache performance, adds overhead, and also increases the cost of copying the structure. Something like boost's flat_map or Abseil's btree_map is likely to be more efficient.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)