[ 
https://issues.apache.org/jira/browse/BEAM-4070?focusedWorklogId=91810&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-91810
 ]

ASF GitHub Bot logged work on BEAM-4070:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 17/Apr/18 16:40
            Start Date: 17/Apr/18 16:40
    Worklog Time Spent: 10m 
      Work Description: aaltay commented on issue #5134: [BEAM-4070]: Make 
cython: profile=False by default
URL: https://github.com/apache/beam/pull/5134#issuecomment-382061289
 
 
   > At least, I prefer to disable profiling in DataflowDistributionCounter 
since I'll call it very often in new features. How about just disable profiling 
in distribution counter first and leave others into further discussion?
   
   I disagree with this. We can either look at macro benchmarks, and understand 
the impact first and make a global decision or postpone this decision. I would 
not make a decision based on the currently available information.

----------------------------------------------------------------
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:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 91810)
    Time Spent: 1h 50m  (was: 1h 40m)

> Disable cython profiling by default
> -----------------------------------
>
>                 Key: BEAM-4070
>                 URL: https://issues.apache.org/jira/browse/BEAM-4070
>             Project: Beam
>          Issue Type: Task
>          Components: sdk-py-core
>            Reporter: Boyuan Zhang
>            Assignee: Boyuan Zhang
>            Priority: Major
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> Enabling cython profiling adds some overhead.
> http://cython.readthedocs.io/en/latest/src/tutorial/profiling_tutorial.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to