From: Linos <info@linos.es>
To: Ross J. Reedstrom <reedstrm@rice.edu>
To: pgsql-performance@postgresql.org
Subject: Re: TCP network cost
Date: Sun, 01 Mar 2009 18:32:28 +0100
Message-ID: <49AAC6AC.60309@linos.es> (raw)
In-Reply-To: <20090224170201.GA25420@cooker>
References: <1ca1c1410902171013q478f2620n13fcd68cb8b3d911@mail.gmail.com>
<20090217070403.GB2486@cooker>
<3FAF940B-9B0B-4DBA-8728-6096022129DF@infogears.com>
<alpine.DEB.1.10.0902170032440.25606@asgard.lang.hm>
<20090217070403.GB2486@cooker>
<3FAF940B-9B0B-4DBA-8728-6096022129DF@infogears.com>
<20090217200416.GA23707@cooker>
<87hc2r272g.fsf@oxford.xeocode.com>
<20090223194212.GA14802@cooker>
<27042.1235423820@sss.pgh.pa.us>
<20090224170201.GA25420@cooker>
Ross J. Reedstrom escribió:
> Excellent. I'll take a look at this and report back here.
>
> Ross
>
>
> On Mon, Feb 23, 2009 at 04:17:00PM -0500, Tom Lane wrote:
>> "Ross J. Reedstrom" <reedstrm@rice.edu> writes:
>>> Summary: C client and large-object API python both send bits in
>>> reasonable time, but I suspect there's still room for improvement in
>>> libpq over TCP: I'm suspicious of the 6x difference. Detailed analysis
>>> will probably find it's all down to memory allocation and extra copying
>>> of bits around (client side)
>> I wonder if the backend isn't contributing to the problem too. It chops
>> its sends up into 8K units, which doesn't seem to create huge overhead
>> in my environment but maybe it does in yours. It'd be interesting to see
>> what results you get from the attached quick-and-dirty patch (against
>> HEAD, but it should apply back to at least 8.1).
>>
>> regards, tom lane
>
Hello, i have been having a problem like this in debian machines and i have
discovered that (almost in my case), the problem only arises when i am using
"ssl = true" in postgresql.conf although i am using clear tcp connections to
localhost to perform my query, if i disable ssl in configuration my localhost
query times goes from 4200ms to 110ms, the same parameter does not have this
effect in my Arch Linux development machine, so maybe you should see how this
parameter affect your setup Ross. My original post to general list is in
http://archives.postgresql.org/pgsql-general/2009-02/msg01297.php for more
information.
Regards,
Miguel Angel.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: info@linos.es, reedstrm@rice.edu
Subject: Re: TCP network cost
In-Reply-To: <49AAC6AC.60309@linos.es>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox