Re: Limit connections to tomcat via mod_jk
On 04.02.2009 14:13, ben short wrote: Hi, We have Apache Httpd 2.4.4 in front of Tomcat 6.0.13 and are using mod_jk to talk between them. Apache Httpd is using prefork configured to allow 256 processes. Tomcat also has 256 threads available. When a user requests a page one call to the Tomcat is made followed by many requests to get static content served up by Apache Httpd. When under load we find that pages take a long time to load due to the number of requests. We believe that by increasing the number of Apache Httpd processes available the pages should load faster as the majority of requests are for static content. What we need to be able to do is limit the number of concurrent requests from Apache Httpd to Tomcat. Meaning that we could have 768 Apache processes available for static content and 256 threads for tomcat. That would be a limiter for the busy value. What would you expect as a response, once the limit is reached? When an additional dynamic request comes in, should it wait for some time, or directly return an error to free the httpd thread for handling static requests? Note: Although often 80% of all requests are for static content, since static content is so much faster (when not being huge), often much less than 50% of all active requests are for static content. And once your dynamic handling capacity is full, what would it help to still be able to serve static content? Of course in case your static content isn't related to the webapps, the story is different. But then you should consider using a separate httpd instance. Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Limit connections to tomcat via mod_jk
Hi, We have Apache Httpd 2.4.4 in front of Tomcat 6.0.13 and are using mod_jk to talk between them. Apache Httpd is using prefork configured to allow 256 processes. Tomcat also has 256 threads available. When a user requests a page one call to the Tomcat is made followed by many requests to get static content served up by Apache Httpd. When under load we find that pages take a long time to load due to the number of requests. We believe that by increasing the number of Apache Httpd processes available the pages should load faster as the majority of requests are for static content. What we need to be able to do is limit the number of concurrent requests from Apache Httpd to Tomcat. Meaning that we could have 768 Apache processes available for static content and 256 threads for tomcat. Is something like this possible? Regards Ben Short -- View this message in context: http://www.nabble.com/Limit-connections-to-tomcat-via-mod_jk-tp21829639p21829639.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Limit connections to tomcat via mod_jk
Hi, We have Apache Httpd 2.4.4 in front of Tomcat 6.0.13 and are using mod_jk to talk between them. Apache Httpd is using prefork configured to allow 256 processes. Tomcat also has 256 threads available. When a user requests a page one call to the Tomcat is made followed by many requests to get static content served up by Apache Httpd. When under load we find that pages take a long time to load due to the number of requests. We believe that by increasing the number of Apache Httpd processes available the pages should load faster as the majority of requests are for static content. What we need to be able to do is limit the number of concurrent requests from Apache Httpd to Tomcat. Meaning that we could have 768 Apache processes available for static content and 256 threads for tomcat. Is something like this possible? Regards Ben Short - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
