hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-10662) Optimize UTF8 string/byte conversions
Date Thu, 04 Aug 2016 14:21:20 GMT

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

Kihwal Lee commented on HDFS-10662:

Committed it to trunk, but for branch-2,  we have to wait for HDFS-10707.

> Optimize UTF8 string/byte conversions
> -------------------------------------
>                 Key: HDFS-10662
>                 URL: https://issues.apache.org/jira/browse/HDFS-10662
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>         Attachments: HDFS-10662.patch, HDFS-10662.patch.1
> String/byte conversions may take either a Charset instance or its canonical name.  One
might think a Charset instance would be faster due to avoiding a lookup and instantiation
of a Charset, but it's not.  The canonical string name variants will cache the string encoder/decoder
(obtained from a Charset) resulting in better performance.
> LOG4J2-935 describes a real-world performance boost.  I micro-benched a marginal runtime
improvement on jdk 7/8.  However for a 16 byte path, using the canonical name generated 50%
less garbage.  For a 64 byte path, 25% of the garbage.  Given the sheer number of times that
paths are (re)parsed, the cost adds up quickly.

This message was sent by Atlassian JIRA

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

View raw message