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

ASF GitHub Bot commented on DISPATCH-557:
-----------------------------------------

GitHub user ganeshmurthy opened a pull request:

    https://github.com/apache/qpid-dispatch/pull/128

    DISPATCH-557 - Moved management of connections from python agent to r…

    …outer core

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

    $ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-557-3

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

    https://github.com/apache/qpid-dispatch/pull/128.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 #128
    
----
commit 6b1bc4d3dc027730c5aa58c7c9d41697f7a478b1
Author: Ganesh Murthy <[email protected]>
Date:   2016-12-12T21:30:38Z

    DISPATCH-557 - Moved management of connections from python agent to router 
core

----


> High connection rates cause problems in the Python management agent
> -------------------------------------------------------------------
>
>                 Key: DISPATCH-557
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-557
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Management Agent
>    Affects Versions: 0.7.0
>            Reporter: Ted Ross
>            Assignee: Ganesh Murthy
>            Priority: Critical
>             Fix For: 0.8.0
>
>
> Since connection entities are the only non-configuration (spontaneously 
> occurring) entities that are still managed by the Python agent, high rates of 
> opening and closing connections causes large CPU overhead in the agent.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to