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

Sergey Shelukhin commented on HIVE-12675:
-----------------------------------------

I don't know if this is a good idea. With DEBUG level, the amount of other 
logging will increase logging dramatically, which affects perf a lot with 
log4j.  Many people run clusters and WARN level because even INFO may be too 
much for perf.
Without crafting a special logging configuration, it would only be possible to 
see perflogger output when it's obscured by perf loss from DEBUG logging..

> PerfLogger should log performance metrics at debug level
> --------------------------------------------------------
>
>                 Key: HIVE-12675
>                 URL: https://issues.apache.org/jira/browse/HIVE-12675
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Hari Sankar Sivarama Subramaniyan
>            Assignee: Hari Sankar Sivarama Subramaniyan
>         Attachments: HIVE-12675.1.patch
>
>
> As more and more subcomponents of Hive (Tez, Optimizer) etc are using 
> PerfLogger to track the performance metrics, it will be more meaningful to 
> set the PerfLogger logging level to DEBUG. Otherwise, we will print the 
> performance metrics unnecessarily for each and every query if the underlying 
> subcomponent does not control the PerfLogging via a parameter on its own.



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

Reply via email to