From: Joost Kraaijeveld <J.Kraaijeveld@Askesis.nl>
To: 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 15:35:58 +0200
Message-ID: <1127482558.3524.23.camel@Panoramix> (raw)
In-Reply-To: <4333E4DB.4020206@tweakers.net>
References: <1127458167.2475.105.camel@Panoramix>
<20050923095517.GW14918@mathom.us>
<1127470875.3524.17.camel@Panoramix>
<20050923110500.GX14918@mathom.us>
<4333E4DB.4020206@tweakers.net>
On Fri, 2005-09-23 at 13:19 +0200, Arjen van der Meijden wrote:
> Another suggestion:
> How many indexes and constraints are on the new table?
As mentioned in the first mail: in this tables only primary key
constraints, no other indexes or constraints.
> Drop all of them and recreate them once the table is filled. Of course
> that only works if you know your data will be ok (which is normal for
> imports of already conforming data like database dumps of existing tables).
> This will give major performance improvements, if you have indexes and
> such on the new table.
I will test this a for perfomance improvement, but still, I wonder if ~
100 inserts/second is a reasonable performance for my software/hardware
combination.
--
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, acmmailing@tweakers.net, mstone+postgres@mathom.us
Subject: Re: How to determine cause of performance problem?
In-Reply-To: <1127482558.3524.23.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