[
https://issues.apache.org/jira/browse/BEAM-12127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Whittle updated BEAM-12127:
-------------------------------
Resolution: Fixed
Status: Resolved (was: Open)
> Reduce counter overhead in PCollectionConsumerRegistry.accept
> -------------------------------------------------------------
>
> Key: BEAM-12127
> URL: https://issues.apache.org/jira/browse/BEAM-12127
> Project: Beam
> Issue Type: Bug
> Components: java-fn-execution
> Reporter: Sam Whittle
> Assignee: Sam Whittle
> Priority: P2
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> DelegatingCounter.inc shows up as 21% of cpu on nexmark query 2 benchmark
> under PCollectionConsumerRegistry.accept
> 2% is actual counter incrementing, but the majority is the delegation of
> DelegatingCounter which involves looking up thread-local state and then
> getting the counter for the name from the counter container. However in this
> case the counter container is known and can just be bound when constructing
> the counter instaed of using DelegatingCounter.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
