RE: Benefits of Apache Server
Howdy, Servlet and JSP pages are dynamic resources: java code is executed every time the user requests them. HTML pages, CSS pages, images, .js files are static resources: no code is run to produce them. They are created once and placed on the server, to be served the same to all requests. I would be very careful with a claim like Ms. Smoak's, Apache is... much faster serving static resources as that's highly qualitative. Please provide benchmarks or tests that prove your point, because I don't think it's much faster at serving static resources. Yoav Shapira Millennium ChemInformatics -Original Message- From: Chris Wahl [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 17, 2003 1:14 AM To: Tomcat Users List Subject: Re: Benefits of Apache Server I 'd like to know what does the static resources exactly mean? html? css? javascripts? It's hard to google explanation of static resources. If HTML scripts are generated by servlet (there is no html files in my web app),will apache be a must? Chris TIA - Original Message - From: Wendy Smoak [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, December 17, 2003 8:00 AM Subject: RE: Benefits of Apache Server Could someone point me where I might find what real added benefit (performance, security or otherwise) that I might recieve by integrating Apache with my Tomcat Server? Isn't there a Wiki somewhere? This would be a really good topic for it... Apache is better at CGI, and much faster serving static resources. It's one of those things where if you have to ask, you probably don't need it. :) As long as Tomcat does what you need, don't complicate your life with Apache and the connector. -- Wendy Smoak Application Systems Analyst, Sr. ASU IA Information Resources Management - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Benefits of Apache Server
Yoav wrote: I would be very careful with a claim like Ms. Smoak's, Apache is... much faster serving static resources as that's highly qualitative. Please provide benchmarks or tests that prove your point, because I don't think it's much faster at serving static resources. Retraction! I should have said, Apache is faster at serving static resources than the Tomcat/connector/Apache combination. I've never tested Tomcat alone vs. Apache alone-- Apache was in place here before I started writing webapps. What I have done is looked at having Apache serve images directly rather than placing them underneath each webapp. I use a lot of the same images across webapps, and I prefer to let Tomcat handle the dynamic content while putting images, css files, and javascript files [what I referred to as static resources] under Apache's root. It's the same mindset as using plain-old-HTML tags in a Struts webapp. If there's no dynamic content, why bother to involve a taglib? -- Wendy Smoak Application Systems Analyst, Sr. ASU IA Information Resources Management - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Benefits of Apache Server
Yoav, I would be very careful with a claim like Ms. Smoak's, Apache is... much faster serving static resources as that's highly qualitative. Please provide benchmarks or tests that prove your point, because I don't think it's much faster at serving static resources. Retraction! I should have said, Apache is faster at serving static resources than the Tomcat/connector/Apache combination. I've never tested Tomcat alone vs. Apache alone-- Apache was in place here before I started writing webapps. I think we can all agree that this statement is true. Certainly adding Apache to Tomcat is slower than having Tomcat do the work all by itself. I don't have benchmarks, and I've made the statement Apache is faster for static content tthan Tomcat before, and I still believe it to be true. Here's why: When Apache httpd serves a static resource, it pretty much goes through all the processing required to find out where the file actually is, and then dumps the bytes to the response. I'm pretty sure that it does all this without allocating anything on the heap -- most of the object/data structures necesary for the lookup I'm sure already exist, and the buffer for the response is probably fixed, and probably on the stack. For Tomcat to do the same thing, it's got to create a bunch of objects which later need to be garbage-collected. I'm guessing that the Tomcat devs have streamlined the process so that not all of the ServletRequest objects and all that jazz are created every time, but you still have to create a lot of stuff on the heap (including every String used, like the URL, and maybe some headers, etc.). After that (probably after the response has been sent to the client, which is why the numbers are hard to track down), the GC has to run. I think that I can make the blanket statement that explicit memory management is faster than GC'd memory, since the GC actually to do some work to determine if memory can be freed, while the explicit scheme needs no such processing. I am willing to concede that Apache vs. Tomcat in a direct competition for serving up static content on the same hardware will probably result in timing differences so small as to be insignificant to anyone doing reasonable benchmarking. Lastly, if you have your architecture such that you have crappy machines in front of the application servers to serve static content (so that the app servers don't waste time serving static content), Apache will run must better on them since it requires fewer resources to run nicely. For example, Apache can do quite nicely on a 16MB machine as a web server. Tomcat can't really do that since the JVM is such a monster. -chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Benefits of Apache Server
Two things come to mind: CGI-BIN support that's easy to setup (I've never gotten them working in tomcat) Faster serving of static pages Perl and PHP support (again this can be done other ways, but it's easier this way IMHO) --mikej -=-- mike jackson [EMAIL PROTECTED] -Original Message- From: Sleeper, Jesse [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 16, 2003 2:25 PM To: Tomcat Users List Subject: Benefits of Apache Server Could someone point me where I might find what real added benefit (performance, security or otherwise) that I might recieve by integrating Apache with my Tomcat Server? Thanks, Jester - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Benefits of Apache Server
Could someone point me where I might find what real added benefit (performance, security or otherwise) that I might recieve by integrating Apache with my Tomcat Server? Isn't there a Wiki somewhere? This would be a really good topic for it... Apache is better at CGI, and much faster serving static resources. It's one of those things where if you have to ask, you probably don't need it. :) As long as Tomcat does what you need, don't complicate your life with Apache and the connector. -- Wendy Smoak Application Systems Analyst, Sr. ASU IA Information Resources Management - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Benefits of Apache Server
Its already in the FAQ. http://jakarta.apache.org/tomcat/faq/connectors.html#integrate -Tim Sleeper, Jesse wrote: Could someone point me where I might find what real added benefit (performance, security or otherwise) that I might recieve by integrating Apache with my Tomcat Server? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Benefits of Apache Server
I 'd like to know what does the static resources exactly mean? html? css? javascripts? It's hard to google explanation of static resources. If HTML scripts are generated by servlet (there is no html files in my web app),will apache be a must? Chris TIA - Original Message - From: Wendy Smoak [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Wednesday, December 17, 2003 8:00 AM Subject: RE: Benefits of Apache Server Could someone point me where I might find what real added benefit (performance, security or otherwise) that I might recieve by integrating Apache with my Tomcat Server? Isn't there a Wiki somewhere? This would be a really good topic for it... Apache is better at CGI, and much faster serving static resources. It's one of those things where if you have to ask, you probably don't need it. :) As long as Tomcat does what you need, don't complicate your life with Apache and the connector. -- Wendy Smoak Application Systems Analyst, Sr. ASU IA Information Resources Management - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
