You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by aaltay <gi...@git.apache.org> on 2016/10/10 21:21:37 UTC

[GitHub] incubator-beam pull request #1077: Add profile_memory flag

GitHub user aaltay opened a pull request:

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

    Add profile_memory flag

    Runners with memory profiling support, would use this flag to profile
    the workflow for heap usage.
    
    Renamed the profile flag to profile_cpu flag to make the distinction
    clear.

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

    $ git pull https://github.com/aaltay/incubator-beam heap

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

    https://github.com/apache/incubator-beam/pull/1077.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 #1077
    
----
commit a299c1112810ace23760fc9583dfccdc646e139a
Author: Ahmet Altay <al...@google.com>
Date:   2016-10-10T21:12:51Z

    Add profile_memory flag
    
    Runners with memory profiling support, would use this flag to profile
    the workflow for heap usage.
    
    Renamed the profile flag to profile_cpu flag to make the distinction
    clear.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-beam pull request #1077: Add profile_memory flag

Posted by aaltay <gi...@git.apache.org>.
Github user aaltay closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---