You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Xiaoyu Yao (Jira)" <ji...@apache.org> on 2020/06/19 04:02:00 UTC
[jira] [Resolved] (HDDS-3743) Avoid NetUtils.normalize when get
DatanodeDetails from proto
[ https://issues.apache.org/jira/browse/HDDS-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaoyu Yao resolved HDDS-3743.
------------------------------
Fix Version/s: 0.7.0
Resolution: Fixed
> Avoid NetUtils.normalize when get DatanodeDetails from proto
> ------------------------------------------------------------
>
> Key: HDDS-3743
> URL: https://issues.apache.org/jira/browse/HDDS-3743
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: runzhiwang
> Assignee: runzhiwang
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.7.0
>
> Attachments: om.svg, screenshot-1.png, screenshot-2.png, screenshot-3.png, screenshot-4.png
>
>
> I start a ozone cluster with 1000 datanodes, and run two weeks with heavy workload, and perf om.
> You can find NetUtils.normalize cost 0.17% cpu, because it needs to do Matcher.replaceAll. It happen in the critical path, i.e. lookUpKey when read. we need not to do this when getFromProtoBuf, So we can avoid normalize by check the last character.
> !screenshot-3.png!
> !screenshot-4.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org