You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2012/10/14 14:25:02 UTC

[jira] [Created] (CAMEL-5703) camel-netty - Pool Channels instead of producers to make producer singleton

Claus Ibsen created CAMEL-5703:
----------------------------------

             Summary: camel-netty - Pool Channels instead of producers to make producer singleton
                 Key: CAMEL-5703
                 URL: https://issues.apache.org/jira/browse/CAMEL-5703
             Project: Camel
          Issue Type: Improvement
          Components: camel-netty
            Reporter: Claus Ibsen
            Assignee: Claus Ibsen
             Fix For: 2.11.0


We should favor using a light-weight pool for the channel on the producer, so it can be singleton which is the preferred for better scalability.

And use commons-pool etc which has eviction logic built-in. Then channels which becomes idle can be evicted sooner. 


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CAMEL-5703) camel-netty - Pool Channels instead of producers to make producer singleton

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-5703.
--------------------------------

    Resolution: Fixed

This change requires a dependency change on camel-netty as commons-pool is used now. This makes backporting harder.
                
> camel-netty - Pool Channels instead of producers to make producer singleton
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-5703
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5703
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-netty
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.11.0
>
>
> We should favor using a light-weight pool for the channel on the producer, so it can be singleton which is the preferred for better scalability.
> And use commons-pool etc which has eviction logic built-in. Then channels which becomes idle can be evicted sooner. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CAMEL-5703) camel-netty - Pool Channels instead of producers to make producer singleton

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-5703:
-------------------------------

    Attachment: after-100.png
                after-200.png
                before-100.png
                before-200.png

before and after screenshots with 100 and 200 clients sending 250.000 messages in request/reply with camel-netty.

With 200 clients the before causes problems by creating to frequent new threads and not cleaning up, which cause memory leak/growth on sustained load. Making high scalability an issue.

Going to backport this to 2.10.x branch
                
> camel-netty - Pool Channels instead of producers to make producer singleton
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-5703
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5703
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-netty
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.11.0
>
>         Attachments: after-100.png, after-200.png, before-100.png, before-200.png
>
>
> We should favor using a light-weight pool for the channel on the producer, so it can be singleton which is the preferred for better scalability.
> And use commons-pool etc which has eviction logic built-in. Then channels which becomes idle can be evicted sooner. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CAMEL-5703) camel-netty - Pool Channels instead of producers to make producer singleton

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-5703:
-------------------------------

    Affects Version/s: 2.10.0
        Fix Version/s: 2.10.3
    
> camel-netty - Pool Channels instead of producers to make producer singleton
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-5703
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5703
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-netty
>    Affects Versions: 2.10.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.10.3, 2.11.0
>
>         Attachments: after-100.png, after-200.png, before-100.png, before-200.png
>
>
> We should favor using a light-weight pool for the channel on the producer, so it can be singleton which is the preferred for better scalability.
> And use commons-pool etc which has eviction logic built-in. Then channels which becomes idle can be evicted sooner. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira