From: Rod Taylor <pg@rbt.ca>
To: bsimon@loxane.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Réf. : Re: RE : RE: Postgresql
Date: Wed, 06 Apr 2005 13:18:29 -0400
Message-ID: <1112807909.92363.120.camel@home> (raw)
In-Reply-To: <OFEF8974CD.30C2BF10-ONC1256FDB.005CA8DD-C1256FDB.005DCD66@beauchamp.loxane.fr>
References: <OFEF8974CD.30C2BF10-ONC1256FDB.005CA8DD-C1256FDB.005DCD66@beauchamp.loxane.fr>
On Wed, 2005-04-06 at 19:08 +0200, bsimon@loxane.com wrote:
>
> On our production server, I can insert 5000 tuples in 2100 ms.
>
> Single Xeon 2.6 Ghz
> 2 Gigs ram
> 3ware RAID 5 SATA drives array, 3 drives only :-((
> PG 8.0 - fsync off
>
> I do think inserting 5000 tuples in a second (i.e 5000 insert
> transactions, no bulk load) can be reached with well a configured SCSI
> RAID 10 array.
Yeah, I think that can be done provided there is more than one worker.
My limit seems to be about 1000 transactions per second each with a
single insert for a single process (round trip time down the Fibre
Channel is large) but running 4 simultaneously only drops throughput to
about 900 per process (total of 2400 transactions per second) and the
machine still seemed to have lots of oomph to spare.
Also worth noting is that this test was performed on a machine which as
a noise floor receives about 200 queries per second, which it was
serving during the test.
> Is pgcluster worth giving a try and can it be trusted for in a
> production environnement ?
> Will it be possible to get a sort of real-time application ?
From the design of pgcluster it looks like it adds in a significant
amount of additional communication so expect your throughput for a
single process to drop through the floor.
--
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: pg@rbt.ca, bsimon@loxane.com
Subject: Re: Réf. : Re: RE : RE: Postgresql
In-Reply-To: <1112807909.92363.120.camel@home>
* 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