2009/9/14 Tsirkin Evgeny <tsir...@gmail.com> > We have a very high load ahead of us and one of my co workers suggestied to > run the cgi program using a tomcat in place of apache . > What we have one spare server that we can connect behind our main server > using one of the two options: > 1. setup mod_proxy to pass the cgi request to this backend machine and on > that machine use apache server. > 2. put tomcat on the backend ,make it run cgi and connect it using mod_jk > Note that we can't use load balancer here to put the new machine _together_ > with the production one , > because we have no time to have a full install of _all_ the applications > there & we need another ssl cert for it. > We just want, at the mean time ,put it at the back and redirect some the > traffic there. > So ,which is better for cgi : tomcat or apache? > The one who suggested tomcat have in mind the fact that tomcat is > multithread and we will have less memory footprint with it,hopefully? >
Apache httpd is also multithreaded. If you're expecting a high CGI load, the footprint of your Web server will be the least of your worries - you should be worrying about the footprint of your CGI application ;-). You'll get more benefit from shaving time and space requirements off that application than you will from changing web server. >From your email, you already have experience with Apache httpd. I would use that for two reasons: 1) you already know how it works 2) Tomcat has CGI support, and it's used. However I suspect far more people run CGIs under httpd. I suspect you'll be able to find more information on httpd if you have problems. Good luck, whichever approach you take! - Peter
