httpd and memory usage

[David Banning]

> Moving things like mod_php and mod_perl stuff to FastCGI avoids each
> httpd having a copy of the interpreter and its various data structures
> each, and segments the memory of the interpreters outside httpd so it's
> easier to see what's using the memory; you'll have fewer copies running
> too, since the static:dynamic request ratio isn't normally 1:1.
> 
> Commenting out unused modules in httpd.conf will save some memory.
> 
> You might also consider switching to something like lighttpd, which uses
> a single process that's generally about 1/3 the size of an equivilent
> httpd process.

I like these ideas. Thanks. What is the downside, if any, to using
lighttpd? Is it difficult to configure?