Skip site navigation (1) Skip section navigation (2)

Re: Performance penalty for remote access of postgresql (8.1.3)? any experiance?

From: Florian Weimer <fweimer(at)bfk(dot)de>
To: <guoping(dot)zhang(at)nec(dot)com(dot)au>
Cc: <pgsql-performance(at)postgresql(dot)org>, "Guoping Zhang (E-mail)" <guopingz(at)nstc(dot)nec(dot)com(dot)au>
Subject: Re: Performance penalty for remote access of postgresql (8.1.3)? any experiance?
Date: 2006-07-19 06:30:14
Message-ID: 82irlu2jk9.fsf@mid.bfk.de (view raw or flat)
Thread:
Lists: 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(at)bfk(dot)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

In response to

Responses

pgsql-performance by date

Next:From: Guoping ZhangDate: 2006-07-19 07:33:34
Subject: Re: Performance penalty for remote access of postgresql (8.1.3)? any experiance?
Previous:From: Guoping ZhangDate: 2006-07-19 05:40:02
Subject: Performance penalty for remote access of postgresql (8.1.3)? any experiance?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group