How much slower is serving static content from Tomcat?

See the Tomcat Connector FAQ for some information. For modern versions of Tomcat, the performance difference is much smaller than it used to be. For a low volume site, there is no reason that you cannot supply all content with Tomcat.

1 Moreover, this solution may simplify your configuration / deployment. I have had problems with Apache mucking with my Tomcat HTTP headers that I have never been able to figure out. – Julien Chastang Mar 17 '09 at 17:15.

I agree except in two circumstances Tomcat's SSL using JSSE is noticeably slower. There are native versions that can be plugged in, but that tends to be more painful. In general the SSL is a bit less straightforward than the well-understand Apache Httpd server Fronting with an HTTpd server gives more flexibility re virtual web hosts etc.Tomcat is not as flexible in this regard.

Unsurprisingly it lacks all the options in Apache :). An obvious nice one is built in compression of static files is very easy to add in Apache.It's not hard in tomcat extra, but it's more work. You are mistaken.

Apache Httpd Server is a totally different beast and has no code shared with Tomcqat. If neither is an issue, than yeah use tomcat by itself.

That may, in fact, be something to consider. I'm not sure the volume will make it a priority but if our performance starts to hurt too bad, that might be a tipping point. – Drew Mar 20 '09 at 21:00.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.