But with the server running on one machine and the client running on
another, the two machines being connected by a 100 Mb ethernet, with nothing
else on the network, this test takes 17 minutes to run. I have tried
changing the frequency of COMMIT operations, but with only a small effect.
Are you
I don't think that's the advice being looked for here - if this
behaviour is repeatable, then there is something askew with the inet
protocol.
What is the client application written in? Do you know what version of
the postgres network protocol your driver code is using? Are the
inserts
On Thu, 2004-07-22 at 23:50, William Carney wrote:
Hello,
Using a test client application that performs 10 insert operations on a
table, with the client application running on the same machine as the
Postgres server, I get the following results for the time taken to run the
test:
Aufflick
Sent: Friday, 23 July 2004 3:50 PM
To: Christopher Kings-Lynne
Cc: William Carney; [EMAIL PROTECTED]
Subject: Re: [PERFORM] Performance over a LAN
I don't think that's the advice being looked for here - if this
behaviour is repeatable, then there is something askew with the inet
On Fri, 2004-07-23 at 01:50, William Carney wrote:
Hello,
Using a test client application that performs 10 insert operations on a
table, with the client application running on the same machine as the
Postgres server, I get the following results for the time taken to run the
test:
On Jul 23, 2004, at 3:57 AM, William Carney wrote:
I tested the LAN connection by transferring around some large (150
MByte)
files, and got consistent transfer rates of about 10 MBytes/second in
both
directions without any problems, which is what I would expect. Netstat
says
It would be
On Fri, Jul 23, 2004 at 03:20:54PM +0930, William Carney wrote:
But with the server running on one machine and the client running on
another, the two machines being connected by a 100 Mb ethernet, with nothing
else on the network, this test takes 17 minutes to run. I have tried
changing the
--- William Carney [EMAIL PROTECTED] wrote:
The test program is a C program with embedded SQL
(ecpg). The only
difference between the tests was the address used in
the EXEC SQL CONNECT
.. statement. The inserts are committed to the
database by performing an
EXEC SQL COMMIT after every N
William Carney [EMAIL PROTECTED] writes:
The machines used are P4s running FreeBSD 5.2.1. The Postgres version is
7.4.3. Can anyone tell me why there's such a big difference?
You're going to have to run tcpdump and see where the delays are. It might be
hard to decode the postgres protocol
