Re: Got no response last time on setsockopt post, so I thought I would reiterate. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Got no response last time on setsockopt post, so I thought I would reiterate.
Date
Msg-id 27664.1181607129@sss.pgh.pa.us
Whole thread Raw
In response to Re: Got no response last time on setsockopt post, so I thought I would reiterate.  ("Dann Corbit" <DCorbit@connx.com>)
Responses Re: Got no response last time on setsockopt post, so I thought I would reiterate.
List pgsql-hackers
"Dann Corbit" <DCorbit@connx.com> writes:
> May I suggest:
> http://www-didc.lbl.gov/TCP-tuning/setsockopt.html
> http://www.ncsa.uiuc.edu/People/vwelch/net_perf/tcp_windows.html

I poked around on those pages and almost immediately came across
http://www.psc.edu/networking/projects/tcptune/
which appears more up-to-date than the other pages, and it specifically
recommends *against* setting SO_SNDBUF or SO_RCVBUF on modern Linuxen.
So that's one fairly large category where we probably do not want this.

You have not even made it clear whether you were increasing the sizes in
the server-to-client or client-to-server direction, and your handwaving
about the test conditions makes it even harder to know what you are
measuring.  I would think for instance that local vs remote connections
make a big difference and might need different tuning.

BTW, if we look at this issue we ought to also look at whether the
send/recv quantum in libpq and the backend should be changed.  It's been
8K for about ten years now ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Selecting a constant question
Next
From: "Dann Corbit"
Date:
Subject: Re: Selecting a constant question