[
https://issues.apache.org/jira/browse/HIVE-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483577#comment-16483577
]
Hive QA commented on HIVE-18866:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12924385/HIVE-18866.04.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 14391 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/11129/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/11129/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-11129/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12924385 - PreCommit-HIVE-Build
> Semijoin: 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)
