You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2020/11/10 00:58:00 UTC

[jira] [Commented] (RATIS-1141) Class.getSimpleName() has a 4% overhead in the SegmentedRaftLogWriter thread

    [ https://issues.apache.org/jira/browse/RATIS-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228888#comment-17228888 ] 

Wei-Chiu Chuang commented on RATIS-1141:
----------------------------------------

Note, this is the same for Ozone Manager.  4~5% overhead.

> Class.getSimpleName() has a 4% overhead in the SegmentedRaftLogWriter thread
> ----------------------------------------------------------------------------
>
>                 Key: RATIS-1141
>                 URL: https://issues.apache.org/jira/browse/RATIS-1141
>             Project: Ratis
>          Issue Type: Improvement
>    Affects Versions: 1.0.0
>            Reporter: Wei-Chiu Chuang
>            Priority: Major
>         Attachments: Screen Shot 2020-11-09 at 3.48.33 PM.png
>
>
> See the attachment. I'm running a write benchmark for Ozone, and the DataNode's SegmentedRaftLogWriter spent 4% time on Class.getSimpleName(). While 4% isn't a lot, Ratis performance is the major bottleneck on the Ozone DN write path. It would be great to remove this overhead.
> Also see https://stackoverflow.com/questions/17369304/why-is-class-getsimplename-not-cached OpenJDK11 caches this call, but not for JDK8 where most of the production workloads are running.



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