7 Replies Latest reply on Dec 20, 2011 7:07 AM by jfclere

How to configure max threads for jbossweb native apr connector (if possible)

kristjan273 Dec 16, 2011 7:29 AM

Hi,

by fixing max-connections (see http://community.jboss.org/message/641746#641746) i can easily create 40k connections on 4Gb heap. I went further and was hoping of trying also performance of apr native jbossweb. I got native libs of version 2.0.10 and made it work with as7.1.0.BETA1b. But surprisingly following happens around ~10k opened connections (same app as before apr test, using async servlet contexts):

INFO  [org.apache.tomcat.util.net.AprEndpoint] (http--10.10.8.3-81-EventPoller) Maximum number of threads (128) created for connector with address /10.10.8.3 and port 81

while by using java based jbossweb 7.0.3:

[org.apache.tomcat.util.net.JIoEndpoint] Maximum number of threads (2048) created for connector with address /10.10.8.3 and port 81

And with apr, further connections are blocked.

As seems to me, some configuration is possible here, but have no idea where to reach it in any of those two cases. I only can see that apr with max threads=128 behaves worse than JIO with 2048.

How should this particular problem be approached?

Thank you in advance,

1. Re: How to configure max threads for jbossweb native apr connector (if possible)

ctomc Dec 17, 2011 7:29 AM (in response to kristjan273)

Hi,

max-connection attribute also works for APR endpoint and should set number of max threads that you need to increase...

please try and let me know,

cheers,
tomaz
Actions
2. Re: How to configure max threads for jbossweb native apr connector (if possible)

kristjan273 Dec 18, 2011 9:26 AM (in response to ctomc)

Hi,

@Tomaz
I have tried the first place, it is the same connector, all the time set up with 'max-connections' to 50000.

Starting without apr, I can reach some ~40k simultaneous connections (heap size 4Gb) while the same config started with apr gives me above info when reaching some ~10k connections. Also my test tool receives timeouts on opening sockets if I try to go above that count
Any idea?
Actions
3. Re: How to configure max threads for jbossweb native apr connector (if possible)

ctomc Dec 19, 2011 6:32 AM (in response to kristjan273)

By looking at code, I would say that setting max-connections to 50000 for APR connector would be suecide, as this setting controls number of working threads. Default is 128.

More than that I don't know how to configure, maybe some guys from jboss web project can/will help you out.
Actions
4. Re: How to configure max threads for jbossweb native apr connector (if possible)

kristjan273 Dec 19, 2011 6:48 AM (in response to ctomc)

Ok, will open the continuation of this question in jbossweb forum (http://community.jboss.org/thread/176313) and stick to jio for now.
Actions
5. Re: How to configure max threads for jbossweb native apr connector (if possible)

jfclere Dec 20, 2011 3:59 AM (in response to kristjan273)

native uses a Poller you should need a huge number of threads to handle a huge number of connections.
max-connections is the parameter to play with usually 128 X cores is a fine value for most application that why that is default.
Actions
6. Re: How to configure max threads for jbossweb native apr connector (if possible)

kristjan273 Dec 20, 2011 5:19 AM (in response to jfclere)

@Jean
Thank you to join this discussion. But I must admit that I don't understand your answer well. Does that mean that native has hardcoded value of the poller size(=128) which multiplies to the number of cores? And is not customizable for different number?

And other thought - If I understand correctly, native is not suitable for solving the problem of large number of open connections (eq. implementing the server push on top of async servlet 3.0), so I should stick to jio based connector?
Actions
7. Re: How to configure max threads for jbossweb native apr connector (if possible)

jfclere Dec 20, 2011 7:07 AM (in response to kristjan273)

128 X cores is the default value, but you can use max-connections to change it.

APR doesn't need on thread per connection it jsut need one thread per active request.
Actions

Go to original post