You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Brahma Reddy Battula (Jira)" <ji...@apache.org> on 2020/04/09 18:48:07 UTC

[jira] [Updated] (HDFS-13701) Removal of logging guards regressed performance

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

Brahma Reddy Battula updated HDFS-13701:
----------------------------------------
    Target Version/s: 3.4.0  (was: 3.3.0)

Bulk update: moved all 3.3.0 non-blocker issues, please move back if it is a blocker.

> Removal of logging guards regressed performance
> -----------------------------------------------
>
>                 Key: HDFS-13701
>                 URL: https://issues.apache.org/jira/browse/HDFS-13701
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: performance
>    Affects Versions: 3.0.0
>            Reporter: Todd Lipcon
>            Priority: Major
>
> HDFS-8971 removed various logging guards from hot methods in the DFS client. In theory using a format string with {} placeholders is equivalent, but in fact it's not equivalent when one or more of the variable arguments are primitives. To be passed as part of the varargs array, the primitives need to be boxed. I am seeing Integer.valueOf() inside BlockReaderLocal.read taking ~3% of CPU.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org