beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (BEAM-4727) Reduce metrics overhead
Date Fri, 06 Jul 2018 19:06:00 GMT


ASF GitHub Bot logged work on BEAM-4727:

                Author: ASF GitHub Bot
            Created on: 06/Jul/18 19:05
            Start Date: 06/Jul/18 19:05
    Worklog Time Spent: 10m 
      Work Description: lostluck commented on issue #5884: [BEAM-4727] Re-use metric context
throughout bundle
   PTAL @wcn3 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 119988)
    Time Spent: 1.5h  (was: 1h 20m)

> Reduce metrics overhead
> -----------------------
>                 Key: BEAM-4727
>                 URL:
>             Project: Beam
>          Issue Type: Sub-task
>          Components: sdk-go
>            Reporter: Robert Burke
>            Assignee: Robert Burke
>            Priority: Major
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
> There are a few opportunities to avoid metrics overhead.
> First when setting state in the context, we allocate a new one for the stored value,
per element. This generates a fair amount of objects for the garbage collector too. If we
retain and re-use contexts within a bundle, we would have the opportunity to save on these
> Also, it's possible that we have overhead on the metric updating paths. We can possibly
do better than the general sync.Map, and avoid the type assertion cost for extracting values
of known types from the maps.

This message was sent by Atlassian JIRA

View raw message