pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alex Turner <armtuk@gmail.com>
To: Merlin Moncure <merlin.moncure@rcsonline.com>
Cc: pgsql-performance@postgresql.org, Arshavir Grigorian <ag@m-cam.com>
Subject: Re: Postgres on RAID5
Date: Mon, 14 Mar 2005 16:42:07 -0500
Message-ID: <33c6269f05031413424d749d5f@mail.gmail.com> (raw)
In-Reply-To: <6EE64EF3AB31D5448D0007DD34EEB3412A763F@Herge.rcsinc.local>
References: <6EE64EF3AB31D5448D0007DD34EEB3412A763F@Herge.rcsinc.local>

He doesn't have a RAID controller, it's software RAID...

Alex Turner
netEconomis


On Mon, 14 Mar 2005 16:18:00 -0500, Merlin Moncure
<merlin.moncure@rcsonline.com> wrote:
> Alex Turner wrote:
> > 35 Trans/sec is pretty slow, particularly if they are only one row at
> > a time.  I typicaly get 200-400/sec on our DB server on a bad day.  Up
> > to 1100 on a fresh database.
> 
> Well, don't rule out that his raid controller is not caching his writes.
> His WAL sync method may be overriding his raid cache policy and flushing
> his writes to disk, always.  Win32 has the same problem, and before
> Magnus's O_DIRECT patch, there was no way to easily work around it
> without turning fsync off.  I'd suggest playing with different WAL sync
> methods before trying anything else.
> 
> Merli
>



view thread (26+ messages)  latest in thread

Message-ID: <33c6269f05031413424d749d5f@mail.gmail.com>
Permalink:  ../33c6269f05031413424d749d5f@mail.gmail.com/
Also on:    postgresql.org/message-id/33c6269f05031413424d749d5f@mail.gmail.com

 · 

reply

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: armtuk@gmail.com, merlin.moncure@rcsonline.com, ag@m-cam.com
  Subject: Re: Postgres on RAID5
  In-Reply-To: <33c6269f05031413424d749d5f@mail.gmail.com>

* 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