On 12.05.2009 02:09, Bill Davidson wrote: >>The 150 threads do not make a good fit to your MaxClients of 256. If >>your Apache is mainly forwarding requests to Tomcat, then it doesn't >>make much sense to allow 256 parallel connections to Apace, but only 150 >>on the backend. That will result in some Apache processes being fully >>connected (32 connections) and some other not able to grow their >>connection pool to the full size, because they get errors when trying to >>connect. > > Interesting. httpd is mainly connecting to servlets but those also request > images, javascript, style sheets and applets that get served directly by > httpd.
Keep in mind, that concurrency = throughput * responsetime So assume 80% of your requests are for static content handled directly by Apache, but those objects might be small and take only 10 milliseconds to handle in the web server (yes, that's not to unlikely), and the 20% requests for dynamic content might take on average 1000 milliseconds, then only 100 * (0.8*10) / (0.8*10 + 0.2*1000) = 4 percent of the observed concurrency will be for static content requests, and 96% for dynamic ones. So you always also need to take the expected response time and the load together to derive some result for concurrency. Regards, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
