camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-5703) camel-netty - Pool Channels instead of producers to make producer singleton
Date Wed, 17 Oct 2012 09:46:03 GMT

     [ 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

Mime
View raw message