[
https://issues.apache.org/jira/browse/HDFS-13703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wang updated HDFS-13703:
-------------------------------
Resolution: Fixed
Fix Version/s: 3.0.4
3.1.1
3.2.0
Status: Resolved (was: Patch Available)
Committed to trunk, branch-3.1, branch-3.0, thanks for working on this Todd!
> Avoid allocation of CorruptedBlocks hashmap when no corrupted blocks are hit
> ----------------------------------------------------------------------------
>
> Key: HDFS-13703
> URL: https://issues.apache.org/jira/browse/HDFS-13703
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: performance
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Major
> Fix For: 3.2.0, 3.1.1, 3.0.4
>
> Attachments: hdfs-13703.patch, hdfs-13703.patch
>
>
> The DFSClient creates a CorruptedBlocks object, which contains a HashMap, on
> every read call. In most cases, a read will not hit any corrupted blocks, and
> this hashmap is not used. It seems the JIT isn't smart enough to eliminate
> this allocation. We would be better off avoiding it and only allocating in
> the rare case when a corrupt block is hit.
> Removing this allocation reduced CPU usage of a TeraValidate job by about 10%.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
