Re: Réf. : Re: RE : RE: Postgresql

From: Rod Taylor <pg(at)rbt(dot)ca>
To: bsimon(at)loxane(dot)com
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Réf. : Re: RE : RE: Postgresql
Date: 2005-04-06 17:18:29
Message-ID: 1112807909.92363.120.camel@home
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Wed, 2005-04-06 at 19:08 +0200, bsimon(at)loxane(dot)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.

--

In response to

Responses

  • Re: Réf at 2005-04-06 17:42:54 from Steinar H. Gunderson

Browse pgsql-performance by date

  From Date Subject
Next Message Arjen van der Meijden 2005-04-06 17:40:29 Re: Plan for relatively simple query seems to be very inefficient
Previous Message bsimon 2005-04-06 17:08:46 Réf. : Re: RE : RE: Postgresql vs SQLserver for this