Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 48322200D4F for ; Wed, 6 Dec 2017 22:08:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 46C4E160C1D; Wed, 6 Dec 2017 21:08:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8D4AA160BF3 for ; Wed, 6 Dec 2017 22:08:04 +0100 (CET) Received: (qmail 8822 invoked by uid 500); 6 Dec 2017 21:08:03 -0000 Mailing-List: contact commits-help@beam.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@beam.apache.org Delivered-To: mailing list commits@beam.apache.org Received: (qmail 8813 invoked by uid 99); 6 Dec 2017 21:08:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Dec 2017 21:08:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 0B3AE1807A6 for ; Wed, 6 Dec 2017 21:08:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id TJh1dXzjQOZt for ; Wed, 6 Dec 2017 21:08:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 73FE65F2C2 for ; Wed, 6 Dec 2017 21:08:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id B613AE0AA3 for ; Wed, 6 Dec 2017 21:08:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 795E9255C9 for ; Wed, 6 Dec 2017 21:08:00 +0000 (UTC) Date: Wed, 6 Dec 2017 21:08:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: commits@beam.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (BEAM-3042) Add tracking of bytes read / time spent when reading side inputs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 06 Dec 2017 21:08:05 -0000 [ https://issues.apache.org/jira/browse/BEAM-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280916#comment-16280916 ] ASF GitHub Bot commented on BEAM-3042: -------------------------------------- pabloem opened a new pull request #4222: [BEAM-3042] Updating Dataflow Api protos URL: https://github.com/apache/beam/pull/4222 This is necessary to be able to report the new Dataflow metrics. r: @chamikaramj ---------------------------------------------------------------- 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: users@infra.apache.org > 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 > > 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 (v6.4.14#64029)