FreeBSD Install config

[Paul Civati]

Paul Robinson <paul at iconoplex.co.uk> wrote:

> Added to that, if you're running a high-traffic site (a million
> page views or more per day - not hits, page views) then you are
> going to get more cacheing going on, and you're going to NEED
> that cacheing if you're running it all on relatively cheap
> hardware - I have fcgi PHP process running on one 

Performance can be helped by putting an "accelarator" or "reverse"
proxy like Squid in front of your main httpd.  Not ideal for all
situations, but can be useful.

> 1. Apache doesn't use much memory because it's not very well written

I'm sure it will use plenty of memory if you configure it correctly
to spawn and pre-spawn enough handler processes.

> 3. Nobody at Apache cares about this

Read "they don't agree with my opinion" :) I'm sure they care a lot
about performance and have gone to great lengths to ensure it's as
fast as it can be, for the design of server it is (ie. forking vs.
select/threading like thttpd/Zeus).

> However, if you're a webhosting firm with say a few hundred
> websites minimum, some of them quite chunky, some of them quite
> popular, you'll start to notice the difference.

Sure.. Apache might not be the best but I think your comments
are a little harsh.  Apache can be configured to perform quite
reasonably if the config and server have been appropriately
tuned.  There is some documentation on the Apache site about
how to optimise things.

-Paul-