You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "László Bodor (Jira)" <ji...@apache.org> on 2020/04/25 16:21:00 UTC

[jira] [Commented] (TEZ-4155) Remove sync bottleneck in counters

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

László Bodor commented on TEZ-4155:
-----------------------------------

the idea of  [^TEZ-4155.01.patch]  was to completely remove lazy-ish ensureInitialized calls, as it's more expensive to synchronize on it in non-sync methods (e.g. filterCounterName) than to just provide a statically initialized conf object I think

> Remove sync bottleneck in counters
> ----------------------------------
>
>                 Key: TEZ-4155
>                 URL: https://issues.apache.org/jira/browse/TEZ-4155
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Rajesh Balamohan
>            Assignee: László Bodor
>            Priority: Trivial
>         Attachments: TEZ-4155.01.patch, image-2020-04-24-13-45-56-187.png
>
>
> [https://github.com/apache/tez/blob/master/tez-api/src/main/java/org/apache/tez/common/counters/Limits.java#L40]
>  
> All blue blocks are due to Limits.java sync.
>  
> !image-2020-04-24-13-45-56-187.png|width=1042,height=734!



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