Performance degradation when more concurrent client request

[Benoit Perroud]

Keeping a max_pool to something around number_of_core * 2 or * 4 could 
be a good idea.

Using an ExecutionHandler to process your message (and free the IO 
workers) is another way to investigate.

In your present case, I would add a logger step in the pipeline to see 
where are going the messages.

Kind regards,

Benoit.

On 05/05/2011 09:31 PM, mubarak.seyed wrote:
> When we use 30 concurrent client request to Netty server, the response gets
> blocked for around 10 seconds and i could not see any exceptions in netty
> log.
>
> When i increase the concurrent threads, response gets timed out.
> What could be an issue?
>
> We are using OrderedMemoryAwareThreadPoolExecutor.
>
> The configurations are as follows
>
> <p>
> max_pool=200 (core thread pool size)
> max_channel_memory=1048576
> max_total_memory=1073741824
> keep_alive_time=100
> connection_number=100 (max connection number for server channel factory)
> connection_time_out=10000
>
> The code would look like
>
>   final OrderedMemoryAwareThreadPoolExecutor pipelineExecutor = new
> OrderedMemoryAwareThreadPoolExecutor(
>                  200,
>                  1048576,
>                  1073741824,
>                  100,
>                  10000, Executors.defaultThreadFactory());
>
>          bootstrap
>                  .setPipelineFactory(new ServerChannelPipelineFactory(
>                          channelGroup,
>                          pipelineExecutor,
>                          queue,
>                          100, //max connection
>                          address, socAddress.getPort()));
>
>
>          bootstrap.setOption("child.tcpNoDelay", true);
>          bootstrap.setOption("child.keepAlive", true);
>          bootstrap.setOption("child.reuseAddress", true);
>          bootstrap.setOption("child.connectTimeoutMillis", 10000);
>          bootstrap.setOption("readWriteFair", true);
>
> </p>
>
> Thanks,
> Mubarak
>
> --
> View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Performance-degradation-when-more-concurrent-client-request-tp6335388p6335388.html
> Sent from the Netty User Group mailing list archive at Nabble.com.
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users