pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: Greg Stark <gsstark@mit.edu>
Cc: Arshavir Grigorian <ag@m-cam.com>
Cc: linux-raid@vger.kernel.org
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres on RAID5 (possible sync blocking read type
Date: Mon, 14 Mar 2005 07:44:53 +0000
Message-ID: <423540F5.8090609@dgreaves.com> (raw)
In-Reply-To: <87hdje7sjm.fsf@stark.xeocode.com>
References: <4231F5F2.6000509@m-cam.com>
	<87hdje7sjm.fsf@stark.xeocode.com>

Greg Stark wrote:

>Arshavir Grigorian <ag@m-cam.com> writes:
>
>  
>
>>Hi,
>>
>>I have a RAID5 array (mdadm) with 14 disks + 1 spare. This partition has an
>>Ext3 filesystem which is used by Postgres. 
>>    
>>
>
>People are going to suggest moving to RAID1+0. I'm unconvinced that RAID5
>across 14 drivers shouldn't be able to keep up with RAID1 across 7 drives
>though. It would be interesting to see empirical data.
>
>One thing that does scare me is the Postgres transaction log and the ext3
>journal both sharing these disks with the data. Ideally both of these things
>should get (mirrored) disks of their own separate from the data files.
>
>But 2-3s pauses seem disturbing. I wonder whether ext3 is issuing a cache
>flush on every fsync to get the journal pushed out. This is a new linux
>feature that's necessary with ide but shouldn't be necessary with scsi.
>
>It would be interesting to know whether postgres performs differently with
>fsync=off. This would even be a reasonable mode to run under for initial
>database loads. It shouldn't make much of a difference with hardware like this
>though. And you should be aware that running under this mode in production
>would put your data at risk.
>
Hi
I'm coming in from the raid list so I didn't get the full story.

May I ask what kernel?

I only ask because I upgraded to 2.6.11.2 and happened to be watching 
xosview on my (probably) completely different setup (1Tb xfs/lvm2/raid5 
served by nfs to a remote sustained read/write app), when I saw all read 
activity cease for 2/3 seconds whilst the disk wrote, then disk read 
resumed. This occured repeatedly during a read/edit/write of a 3Gb file.

Performance not critical here so on the "hmm, that's odd" todo list :)

David




Message-ID: <423540F5.8090609@dgreaves.com>
Permalink:  ../423540F5.8090609@dgreaves.com/
Also on:    postgresql.org/message-id/423540F5.8090609@dgreaves.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: david@dgreaves.com, gsstark@mit.edu, ag@m-cam.com, linux-raid@vger.kernel.org
  Subject: Re: Postgres on RAID5 (possible sync blocking read type
  In-Reply-To: <423540F5.8090609@dgreaves.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