ASF GitHub Bot logged work on BEAM-3042:

                Author: ASF GitHub Bot
            Created on: 11/Apr/18 15:49
            Start Date: 11/Apr/18 15:49
    Worklog Time Spent: 10m 
      Work Description: pabloem commented on issue #5075: [BEAM-3042] Refactor 
of TransformIOCounters (performance, inheritance). Time counter for sideinputs.
URL: https://github.com/apache/beam/pull/5075#issuecomment-380501780
   After running 5 jobs with the sideinputs_iterable_windowed_benchmark_python 
with the changes activated in a sandbox environment, we get (all in minutes):
   > Runtime
   > 11.23    
   > 11.47    
   > 10.82    
   > 10.89   
   > 11.57    
   AVG: 11.196
   STD: 0.30037
   From the latest 25 runs of this benchmark, we have:
   AVG: 10.1248
   STD: 0.881876
   Seeing as this adds a significant amount of overhead, I think we'll start a 
new version for the experiment flag to test in our manageability tests. Sounds 
good Ahmet?

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: 90009)
    Time Spent: 2h 10m  (was: 2h)

> Add tracking of bytes read / time spent when reading side inputs
> ----------------------------------------------------------------
>                 Key: BEAM-3042
>                 URL: https://issues.apache.org/jira/browse/BEAM-3042
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py-core
>            Reporter: Pablo Estrada
>            Assignee: Pablo Estrada
>            Priority: Major
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
> It is difficult for Dataflow users to understand how modifying a pipeline or 
> data set can affect how much inter-transform IO is used in their job. The 
> intent of this feature request is to help users understand how side inputs 
> behave when they are consumed.
> This will allow users to understand how much time and how much data their 
> pipeline uses to read/write to inter-transform IO. Users will also be able to 
> modify their pipelines and understand how their changes affect these IO 
> metrics.
> For further information, please review the internal Google doc 
> go/insights-transform-io-design-doc.

This message was sent by Atlassian JIRA

Reply via email to