From: Joost Kraaijeveld <J.Kraaijeveld@Askesis.nl>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Arjen van der Meijden <acmmailing@tweakers.net>
Cc: Michael Stone <mstone+postgres@mathom.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: How to determine cause of performance problem?
Date: Fri, 23 Sep 2005 16:47:04 +0200
Message-ID: <1127486824.3524.58.camel@Panoramix> (raw)
In-Reply-To: <3711.1127485986@sss.pgh.pa.us>
References: <1127458167.2475.105.camel@Panoramix>
<20050923095517.GW14918@mathom.us>
<1127470875.3524.17.camel@Panoramix>
<20050923110500.GX14918@mathom.us>
<4333E4DB.4020206@tweakers.net>
<1127482558.3524.23.camel@Panoramix>
<3711.1127485986@sss.pgh.pa.us>
On Fri, 2005-09-23 at 10:33 -0400, Tom Lane wrote:
> Is the client code running on the same machine as the database server?
> If not, what's the network delay and latency between them?
Yes, it is running on the same machine.
> The major problem you're going to have here is at least one network
> round trip per row inserted --- possibly more, if the jdbc driver is
> doing "helpful" stuff behind your back like starting/committing
> transactions.
OK, I will look into that.
But do you maybe know a pointer to info, or tools that can measure, what
my machine is doing during all the time it is doing nothing? Something
like the performance monitor in Windows but than for Linux?
--
Groeten,
Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06-51855277
fax: 024-3608416
e-mail: J.Kraaijeveld@Askesis.nl
web: www.askesis.nl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: J.Kraaijeveld@Askesis.nl, tgl@sss.pgh.pa.us, acmmailing@tweakers.net, mstone+postgres@mathom.us
Subject: Re: How to determine cause of performance problem?
In-Reply-To: <1127486824.3524.58.camel@Panoramix>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox