Re: PostgreSQL pre-fork speedup - Mailing list pgsql-hackers

From James Robinson
Subject Re: PostgreSQL pre-fork speedup
Date
Msg-id E33AE550-9F7F-11D8-9C07-000A9566A412@socialserve.com
Whole thread Raw
In response to Re: PostgreSQL pre-fork speedup  (sdv mailer <sdvmailer@yahoo.com>)
Responses Re: PostgreSQL pre-fork speedup  (sdv mailer <sdvmailer@yahoo.com>)
Re: PostgreSQL pre-fork speedup  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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 by date:

Previous
From: sdv mailer
Date:
Subject: Re: PostgreSQL pre-fork speedup
Next
From: sdv mailer
Date:
Subject: Re: PostgreSQL pre-fork speedup