Re: Pooling in Core WAS: Need help in performance tuning.
От | Robert Haas |
---|---|
Тема | Re: Pooling in Core WAS: Need help in performance tuning. |
Дата | |
Msg-id | AANLkTikG_QqNXmGaAtnChGHyVAhdSosoE5M3MXwDKMH8@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Pooling in Core WAS: Need help in performance tuning. (Craig Ringer <craig@postnewspapers.com.au>) |
Ответы |
Re: Pooling in Core WAS: Need help in performance tuning.
|
Список | pgsql-performance |
On Mon, Jul 12, 2010 at 6:58 AM, Craig Ringer <craig@postnewspapers.com.au> wrote: > On 12/07/10 17:45, Matthew Wakeling wrote: >> >> I'm surprised. Doesn't apache httpd do this? Does it have to do a whole >> load of non-portable stuff? It seems to work on a whole load of platforms. > > A lot of what Apache HTTPd does is handled via the Apache Portable > Runtime (APR). It contains a lot of per-platform handlers for various > functionality. Apache just has all of the worker processes call accept() on the socket, and whichever one the OS hands it off to gets the job. The problem is harder for us because a backend can't switch identities once it's been assigned to a database. I haven't heard an adequate explanation of why that couldn't be changed, though. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
В списке pgsql-performance по дате отправления: