beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-255) Understand and improve performance of Write/FileBasedSink
Date Tue, 03 May 2016 20:08:12 GMT

    [ https://issues.apache.org/jira/browse/BEAM-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269481#comment-15269481
] 

ASF GitHub Bot commented on BEAM-255:
-------------------------------------

GitHub user dhalperi opened a pull request:

    https://github.com/apache/incubator-beam/pull/279

    [BEAM-255] Write: add limited logging

    This will help, for all sinks, users and developers gain insight into where time
    is spent. (Enabling DEBUG level will provide more insight.)
    
    R: @lukecwik 


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dhalperi/incubator-beam write-logging

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-beam/pull/279.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #279
    
----
commit d892f259cb9dd33b762aca416d9b616423c5fbae
Author: Dan Halperin <dhalperi@google.com>
Date:   2016-05-03T20:07:04Z

    [BEAM-255] Write: add limited logging
    
    This will help, for all sinks, users and developers gain insight into where time
    is spent. (Enabling DEBUG level will provide more insight.)

----


> Understand and improve performance of Write/FileBasedSink
> ---------------------------------------------------------
>
>                 Key: BEAM-255
>                 URL: https://issues.apache.org/jira/browse/BEAM-255
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-gcp
>            Reporter: Daniel Halperin
>            Assignee: Daniel Halperin
>
> The work by [~lcwik] to move TextIO from a Dataflow-specific implementation to a FileBasedSink-based
implementation may have caused performance regressions -- which really means it has exposed
opportunity for improvement in the Beam combination of Write/FileBasedSink.
> This is a general tracking bug for SDK-side improvements (likely GCP-related).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message