I tried to use only Tomcat since the static content is dynamically generated. Think blogging application.
However, users dont update the data that often, that's why I generate the content and make it static for web access, as oppose to dynamically generate the content each time it is requested. Using minimal CPU cycles. Also, I tried to use ONLY Tomcat and do away with integration of Apache HTTP + Tomcat, or Lighthttpd + Tomcat, because its would be easier to maintain. I will try to write some tests and see how much memory and such. Then post back here. This may take a while. Worse come to worst, I will keep only 1 webapp, then use servlet filter to return different HTML depending on the httpServletRequest.getServerName(). ~KEGan On 8/26/06, Mladen Turk <[EMAIL PROTECTED]> wrote:
Andrew Miehs wrote: > > If you are only delivering static content, then use Apache or Lighttpd > > http://www.lighttpd.net/ > > This is NOT what tomcat is designed for.... > In theory the threaded model should consume less memory and less CPU cycles compared with prefork model. Of course if your application is stable then you should always prefer worker-mpm over the prefork-mpm. Did you ever tried to hit the Httpd with 10000 concurrent connections? I did, and Tomcat uses less memory then Apache httpd, and that's why it is 2 times faster then httpd. Regards, Mladen. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
