From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: TCP network cost |
Date: | 2009-02-23 21:17:00 |
Message-ID: | 27042.1235423820@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
"Ross J. Reedstrom" <reedstrm(at)rice(dot)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
Attachment | Content-Type | Size |
---|---|---|
unknown_filename | text/plain | 2.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Farhan Husain | 2009-02-23 23:16:22 | Abnormal performance difference between Postgres and MySQL |
Previous Message | david | 2009-02-23 21:02:38 | Re: postgreSQL performance 8.2.6 vs 8.3.3 |