Re: Performance penalty for remote access of postgresql (8.1.3)? any experiance? - Mailing list pgsql-performance

From Florian Weimer
Subject Re: Performance penalty for remote access of postgresql (8.1.3)? any experiance?
Date
Msg-id 82irlu2jk9.fsf@mid.bfk.de
Whole thread Raw
In response to Performance penalty for remote access of postgresql (8.1.3)? any experiance?  ("Guoping Zhang" <guoping.zhang@nec.com.au>)
Responses Re: Performance penalty for remote access of postgresql (8.1.3)? any experiance?  ("Guoping Zhang" <guoping.zhang@nec.com.au>)
List pgsql-performance
* Guoping Zhang:

>   a) Anyone has the similar experience? How do you deal with it?
>   b) Why TCP stack imposes such big delay? any tuning point I shall do?

If you use INSERT, you'll incur a network round-trip delay for each
record.  Try using COPY FROM instead, possibly to a temporary table if
you need more complex calculations.  If you do this, there won't be a
huge difference between local and remote access as long as the
bandwidth is sufficient.

--
Florian Weimer                <fweimer@bfk.de>
BFK edv-consulting GmbH       http://www.bfk.de/
Durlacher Allee 47            tel: +49-721-96201-1
D-76131 Karlsruhe             fax: +49-721-96201-99

pgsql-performance by date:

Previous
From: "Guoping Zhang"
Date:
Subject: Performance penalty for remote access of postgresql (8.1.3)? any experiance?
Next
From: "Guoping Zhang"
Date:
Subject: Re: Performance penalty for remote access of postgresql (8.1.3)? any experiance?