You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2018/05/22 19:54:00 UTC
[jira] [Commented] (HIVE-18866) Semijoin and analyze: Implement a
Long -> Hash64 vector fast-path
[ https://issues.apache.org/jira/browse/HIVE-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484474#comment-16484474 ]
Sergey Shelukhin commented on HIVE-18866:
-----------------------------------------
Committed to master, branch-3 commit is blocked due to storage-api version mismatch, I will file a JIRA
> Semijoin and analyze: Implement a Long -> Hash64 vector fast-path
> -----------------------------------------------------------------
>
> Key: HIVE-18866
> URL: https://issues.apache.org/jira/browse/HIVE-18866
> Project: Hive
> Issue Type: Improvement
> Components: Vectorization
> Reporter: Gopal V
> Assignee: Sergey Shelukhin
> Priority: Major
> Labels: performance
> Attachments: 0001-hash64-WIP.patch, HIVE-18866.01.patch, HIVE-18866.02.patch, HIVE-18866.03.patch, HIVE-18866.04.patch, HIVE-18866.patch, perf-hash64-long.png
>
>
> A significant amount of CPU is wasted with JMM restrictions on byte[] arrays.
> To transform from one Long -> another Long, this goes into a byte[] array, which shows up as a hotspot.
> !perf-hash64-long.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)