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

Posted to issues@beam.apache.org by "Robert Burke (Jira)" <ji...@apache.org> on 2020/01/23 01:21:00 UTC

[jira] [Assigned] (BEAM-6498) Consider using sync/atomic for Go SDK metrics.

     [ https://issues.apache.org/jira/browse/BEAM-6498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Burke reassigned BEAM-6498:
----------------------------------

    Assignee: Robert Burke

> Consider using sync/atomic for Go SDK metrics.
> ----------------------------------------------
>
>                 Key: BEAM-6498
>                 URL: https://issues.apache.org/jira/browse/BEAM-6498
>             Project: Beam
>          Issue Type: Sub-task
>          Components: sdk-go
>    Affects Versions: Not applicable
>            Reporter: Robert Burke
>            Assignee: Robert Burke
>            Priority: Minor
>
> Changing a portion of the metrics code to use the atomic counters might yield a performance improvement and the opportunity to remove a lock or two.
> Care needs to be taken though: [https://stackoverflow.com/questions/47445344/is-there-a-difference-in-go-between-a-counter-using-atomic-operations-and-one-us]
> The outcome of this task is a benchmark demonstrating the benefit (or detriment) in a quasi-real situation for the Go SDK, and if warranted switching metrics where possible, to use atomics.



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