Mark Rudholm wrote:
The result, however, is that Gentoo becomes an inappropriate
choice for a production server deployment. I haven't suggested
Gentoo for production servers to anyone (especially my employers)
since somewhere around 2003 for this reason.
Strange as that's the year I started pushing Gentoo into production.
One of the reasons was it allowed us to keep Apache 1.3 when Redhat,
Suse, etc were forcing 2.0 upon us. We weren't ready at the time, had
some custom Apache 1.3 modules we needed to update, and frankly 2.0
hadn't been around long enough for anyone to trust it.
However we did transition to Apache 2.0 in late 2004 because Apache 1.3
was 10-15% slower, module support was starting to go downhill, and
eventually you do need to update your systems. Being able to run the
content servers multi-threaded was a nice gain as well. Overall the
transition allowed us to grow with 20-25% less hardware than Apache 1.3
would have required. In a system of one hundred servers that's an
elimination of twenty servers, one switch, a ton or so of air
conditioning, half a rack, 40-60A of electric, one KVM, and so on.
You can't run 1.3 forever and IMHO four years has been more than enough
time to decide to update a web server even if you have thousands of them.
kashani
--
[EMAIL PROTECTED] mailing list
