Re: PostgreSQL pre-fork speedup
| От | James Robinson |
|---|---|
| Тема | Re: PostgreSQL pre-fork speedup |
| Дата | |
| Msg-id | E33AE550-9F7F-11D8-9C07-000A9566A412@socialserve.com обсуждение исходный текст |
| Ответ на | Re: PostgreSQL pre-fork speedup (sdv mailer <sdvmailer@yahoo.com>) |
| Ответы |
Re: PostgreSQL pre-fork speedup
Re: PostgreSQL pre-fork speedup |
| Список | pgsql-hackers |
Quick overview of the code for differences in TCP-on-the-frontend code is a call to setsockopt(..., TCP_NODELAY, ...) if the connection to the frontend is a TCP socket. Could this be producing pseudo-fragmentation, resulting in over-the-top context switches? Looks like pool_process_query() does a lot of little itty bitty writes to the frontend filedescriptor. What do you get if you comment out that block in child.c, around line 372? Either a faster system or a non-working one? ---- James Robinson Socialserve.com
В списке pgsql-hackers по дате отправления: