| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Axel Waggershauser" <awagger(at)web(dot)de> |
| Cc: | <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Low throughput of binary inserts from windows to |
| Date: | 2006-12-11 16:25:14 |
| Message-ID: | 457D320A.EE98.0025.0@wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
>>> On Mon, Dec 11, 2006 at 8:58 AM, in message
<5e66c6e90612110658r3c0918f6v4fd3682363db5c15(at)mail(dot)gmail(dot)com>, "Axel
Waggershauser" <awagger(at)web(dot)de> wrote:
>
> I'm out of ideas here, maybe someone could try to reproduce this
> behavior or could point me to the thread containing relevant
> information
No guarantees that this is the problem, but I have seen similar issues
in other software because of delays introduced in the TCP stack by the
Nagle algorithm. Turning on TCP_NODELAY has solved such problems. I
don't know if PostgreSQL is vulnerable to this, or how it would be fixed
in a PostgreSQL environment, but it might give you another avenue to
search.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cosimo Streppone | 2006-12-11 16:26:49 | Looking for hw suggestions for high concurrency OLTP app |
| Previous Message | Jens Schipkowski | 2006-12-11 16:19:27 | really quick multiple inserts can use COPY? |