hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gopal V (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-8158) Optimize writeValue/setValue in VectorExpressionWriterFactory (in VectorReduceSinkOperator codepath)
Date Fri, 19 Sep 2014 04:50:34 GMT

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

Gopal V updated HIVE-8158:
--------------------------
      Resolution: Fixed
    Release Note: HIVE-8158: Optimize writeValue/setValue in VectorExpressionWriterFactory
          Status: Resolved  (was: Patch Available)

Committed to trunk, thanks [~rajesh.balamohan]

> Optimize writeValue/setValue in VectorExpressionWriterFactory (in VectorReduceSinkOperator
codepath)
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-8158
>                 URL: https://issues.apache.org/jira/browse/HIVE-8158
>             Project: Hive
>          Issue Type: Bug
>          Components: Vectorization
>    Affects Versions: 0.14.0
>            Reporter: Rajesh Balamohan
>            Assignee: Rajesh Balamohan
>              Labels: performance
>             Fix For: 0.14.0
>
>         Attachments: HIVE-8158.1.patch, profiler_output.png
>
>
> VectorReduceSinkOperator --> ProcessOp --> makeValueWriatable --> VectorExpressionWriterFactory
--> writeValue(byte[], int, int) /setValue.
> It appears that this goes through an additional layer of Text.encode/decode causing CPU
pressure (profiler output attached).
> SettableStringObjectInspector / WritableStringObjectInspector has "set(Object o, Text
value)" method. It would be beneficial to use set(Object, Text) directly to save CPU cycles.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message