[
https://issues.apache.org/jira/browse/HIVE-13027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15196507#comment-15196507
]
Prasanth Jayachandran commented on HIVE-13027:
----------------------------------------------
I tried another query with TPCDS 1TB scale. The runtime for queries at WARN
level and INFO are 18.1s vs 18.5s respectively. One thing I am noticing is that
the presence of disruptor jar in the classpath itself triggers Async logging
without -DLog4jContextSelector system property. I don't know why yet.
> Async loggers for LLAP
> ----------------------
>
> Key: HIVE-13027
> URL: https://issues.apache.org/jira/browse/HIVE-13027
> Project: Hive
> Issue Type: Improvement
> Components: Logging
> Affects Versions: 2.1.0
> Reporter: Prasanth Jayachandran
> Assignee: Prasanth Jayachandran
> Attachments: HIVE-13027.1.patch
>
>
> LOG4j2's async logger claims to have 6-68 times better performance than
> synchronous logger. https://logging.apache.org/log4j/2.x/manual/async.html
> We should use that for LLAP.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
