On 22/08/2014 11:22, anurag gupta wrote: > Executors:- > > <Executor name="tomcatThreadPool" namePrefix="catalina-exec-" > maxThreads="2048" minSpareThreads="1024" maxQueueSize="10000" > prestartminSpareThreads="true"/> > > This is the connector config :- > > <Connector port="8080" > protocol="org.apache.coyote.http11.Http11NioProtocol" redirectPort="8443" > acceptCount="100000" maxConnections="-1" > acceptorThreadCount="5" executor="tomcatThreadPool" > connectionLinger="-1" socket.soLingerOn="false" socket.soLingerTime="0" > socket.soReuseAddress="true" connectionTimeout="1000" > socket.soTimeout="1000" keepAliveTimeout="0" maxKeepAliveRequests="1" > socket.soKeepAlive="false" /> > >> The only way to know for sure is if you use a profiler and find out > where you application is using memory. > > Yes we do cache the AsyncResponse objects till the timeout happens or some > response is generated. > >> How long does a request take to process? Exactly how many concurrent > requests are you trying to support? > A long poll request has a timeout of 10 mins (in this test), but we want to > have it upto 60 mins if feasible. > We are trying to figure out the max achievable concurrent requests.
Concurrent requests != concurrent connections. Concurrent requests (i.e. where the server is actively doing something with a connection) will be limited to 2048 with that configuration (maximum number of available threads). Concurrent connections will depend on you test environment. For a single Tomcat HTTP connector, there is a hard limit of 64k connections per client but you can use multiple clients (each with their own IP address) to get around that. After that, you'll hit OS limits - that should be around several hundred k. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
