Re: Camel Netty could not process on heavy load
You could send the incoming message off to another component(s) with their own thread pools. Also, is there anyway to upgrade your version of Camel? There's a newer version of the Netty component released as of 2.14. On Tue, Sep 27, 2016 at 1:20 AM, jshankarc wrote: > Hi Tadayoshi, > > If we increase workerCount to 50 - 100 system becomes slow. > > From Redhat Team, they are suggesting to keep the workercount between 8-16. > > Thanks, > Jayashankar > > > > > -- > View this message in context: http://camel.465427.n5.nabble. > com/Camel-Netty-could-not-handle-more-request-on-load- > testing-tp5787988p5788086.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
Re: Camel Netty could not process on heavy load
Hi Tadayoshi, If we increase workerCount to 50 - 100 system becomes slow. >From Redhat Team, they are suggesting to keep the workercount between 8-16. Thanks, Jayashankar -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Netty-could-not-handle-more-request-on-load-testing-tp5787988p5788086.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Netty could not process on heavy load
Hello, Why can't you use 'workerCount' option? It overrides the default number of threads for Netty. http://camel.apache.org/netty.html Best regards, Tadayoshi On Sat, Sep 24, 2016 at 3:58 PM, jayashankar wrote: > Using camel netty component redhat version 2.12.X version to consume TCP > requests > > System configuration: 8 Core CPU > > As per my understanding > Boss thread poll will accept the request and ask worker threads poll to > process it. > For each port, 1 Boss Thread and 16 worker threads are available. > > Limitations: >If all worker threads are busy, boss threads will not hand over requests > to process and it will still be waiting for worker thread to be available. >This is impacting our performance, we have to use TCP Protocol and JBoss > Fuse 6.1 but serve more 30 - 50 request per second > > Finding possible solutions by below proxy server: > 1. HAProxy > 2. Nginx > > With these, I am able to accept TCP requests but could not forward HTTP > post > - (Using Camel Jetty Consumer) > > is there any way to over come this problem, please let me know. > > > > -- > View this message in context: http://camel.465427.n5.nabble. > com/Camel-Netty-could-not-process-on-heavy-load-tp5787988.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
Camel Netty could not process on heavy load
Using camel netty component redhat version 2.12.X version to consume TCP requests System configuration: 8 Core CPU As per my understanding Boss thread poll will accept the request and ask worker threads poll to process it. For each port, 1 Boss Thread and 16 worker threads are available. Limitations: If all worker threads are busy, boss threads will not hand over requests to process and it will still be waiting for worker thread to be available. This is impacting our performance, we have to use TCP Protocol and JBoss Fuse 6.1 but serve more 30 - 50 request per second Finding possible solutions by below proxy server: 1. HAProxy 2. Nginx With these, I am able to accept TCP requests but could not forward HTTP post - (Using Camel Jetty Consumer) is there any way to over come this problem, please let me know. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Netty-could-not-process-on-heavy-load-tp5787988.html Sent from the Camel - Users mailing list archive at Nabble.com.
