Re: PostgreSQL pre-fork speedup

From: James Robinson <jlrobins(at)socialserve(dot)com>
To: sdv mailer <sdvmailer(at)yahoo(dot)com>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Subject: Re: PostgreSQL pre-fork speedup
Date: 2004-05-06 17:07:42
Message-ID: E33AE550-9F7F-11D8-9C07-000A9566A412@socialserve.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message sdv mailer 2004-05-06 17:12:57 Re: PostgreSQL pre-fork speedup
Previous Message sdv mailer 2004-05-06 17:06:41 Re: PostgreSQL pre-fork speedup