[jira] [Commented] (HIVE-3706) getBoolVar in FileSinkOperator can be optimized

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547869#comment-13547869 ] 

Hudson commented on HIVE-3706:
------------------------------

Integrated in Hive-trunk-hadoop2 #54 (See [https://builds.apache.org/job/Hive-trunk-hadoop2/54/])
    HIVE-3706 getBoolVar in FileSinkOperator can be optimized
(Kevin Wilfong via namit) (Revision 1409691)

     Result = ABORTED
namit : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1409691
Files : 
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/exec/FileSinkOperator.java

                
> getBoolVar in FileSinkOperator can be optimized
> -----------------------------------------------
>
>                 Key: HIVE-3706
>                 URL: https://issues.apache.org/jira/browse/HIVE-3706
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Processor
>    Affects Versions: 0.10.0
>            Reporter: Kevin Wilfong
>            Assignee: Kevin Wilfong
>             Fix For: 0.10.0
>
>         Attachments: HIVE-3706.1.patch.txt
>
>
> There's a call to HiveConf.getBoolVar in FileSinkOperator's processOp method.  In benchmarks we found this call to be using ~2% of the CPU time on simple queries, e.g. INSERT OVERWRITE TABLE t1 SELECT * FROM t2;
> This boolean value, a flag to collect the RawDataSize stat, won't change during the processing of a query, so we can determine it at initialization and store that value, saving that CPU.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira