* Joshua D. Drake <jd@commandprompt.com> [090512 19:27]:
> Apache solved this problem back when it was still called NSCA HTTPD. Why
> aren't we preforking again?
Of course, preforking and connection pooling are totally different
beast...
But, what really does preforking give us? A 2 or 3% improvement? The
forking isn't the expensive part, the per-database setup that happens is
the expensive setup... All pre-forking would save us is a tiny part of
the initial setup, and in turn make our robust postmaster controller no
longer have control.
a.
--
Aidan Van Dyk Create like a god,
aidan@highrise.ca command like a king,
http://www.highrise.ca/ work like a slave.
