"Pierre C" <li...@peufeu.com> writes: > The same is true of a web server : 1000 active php interpreters (each eating > several megabytes or more) are not ideal for performance ! > > For php, I like lighttpd with php-fastcgi : the webserver proxies requests > to a small pool of php processes, which are only busy while generating the > page. Once the page is generated the webserver handles all (slow) IO to the > client.
I use haproxy for that, it handles requests queues very effectively. -- dim -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
