hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7978) Add LOG.isDebugEnabled() guard for some LOG.debug(..)
Date Tue, 24 Mar 2015 04:29:53 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377256#comment-14377256

Andrew Wang commented on HDFS-7978:

Hey Walter, I'd prefer if we worked on switching over to slf4j in most of these cases, rather
than adding if guards. That saves the string construction cost. I don't think any of the functions
you wrapped in this patch are particularly expensive, but if you disagree we can keep the
if guards.

> Add LOG.isDebugEnabled() guard for some LOG.debug(..)
> -----------------------------------------------------
>                 Key: HDFS-7978
>                 URL: https://issues.apache.org/jira/browse/HDFS-7978
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Walter Su
>            Assignee: Walter Su
>         Attachments: HDFS-7978.001.patch
> {{isDebugEnabled()}} is optional. But when there are :
> 1. lots of concatenating Strings
> 2. complicated function calls
> in the arguments, {{LOG.debug(..)}} should be guarded with {{LOG.isDebugEnabled()}} to
avoid unnecessary arguments evaluation and impove performance.

This message was sent by Atlassian JIRA

View raw message