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-3042) Add tracking of bytes read / time spent when reading side inputs
Date Tue, 10 Apr 2018 16:45:00 GMT


ASF GitHub Bot logged work on BEAM-3042:

                Author: ASF GitHub Bot
            Created on: 10/Apr/18 16:44
            Start Date: 10/Apr/18 16:44
    Worklog Time Spent: 10m 
      Work Description: pabloem commented on issue #5075: [BEAM-3042] Refactor of TransformIOCounters
(performance, inheritance). Time counter for sideinputs.
   Sounds good. Thanks for taking a look.

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: 89485)
    Time Spent: 1h 50m  (was: 1h 40m)

> Add tracking of bytes read / time spent when reading side inputs
> ----------------------------------------------------------------
>                 Key: BEAM-3042
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py-core
>            Reporter: Pablo Estrada
>            Assignee: Pablo Estrada
>            Priority: Major
>          Time Spent: 1h 50m
>  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

View raw message