> -----Original Message----- > From: Power-Netz (Schwarz) [mailto:[EMAIL PROTECTED]] > Sent: Monday, September 09, 2002 1:57 AM > To: Tomcat Users List > Subject: AW: Tomcat standalone Versus Apache > > > > What do most people run for production and why? Tomcat > > standalone or Tomcat > > with Apache? And for that matter, isn't the http server for > > Tomcat Apache - > > or is it something else? >
Apache may be slightly faster at serving static pages, but unless you're running a web site with lots of traffic and lots of static content, I doubt that you will notice any difference compared to running Tomcat stand-alone. In fact, your dynamic pages (servlets and JSP pages) may run slightly slower, because you now have a new layer of code to go through before you hit them. Adding Apache to the mix also makes life a whole lot more complex, as you have already seen. There's rarely a need to run Tomcat behind Apache. The exceptions I can think of are * if your site uses a mix of servlet/JSP and features only supported by Apache (e.g. PHP, mod_rewrite, etc.) * if you make heavy use of HTTPS; Apache's SSL C code is probably still faster than Tomcat's SSL Java code. * if you have an extremely popular site with tons of large static files (e.g. huge graphic files). If none of this is true, I recommend sticking to the stand-alone configurations. Remember that performance is rarely a goal in itself; enough performance to handle your requirements is typically what you want. Performance always cost something (more complex design, configuration and administration, more expensive hardware and software) Run load tests against your site and see if it's able to handle the estimated peek usage within the time margins you define. If so, great. If not, try to find the bottleneck and fix it. In most cases it's the database for a web application, not the web server's ability to serve static files. > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
