From: Yves Vindevogel <yves.vindevogel@implements.be>
To: pgsql-performance@postgresql.org
Subject: Fwd: Multiple disks: RAID 5 or PG Cluster
Date: Sat, 18 Jun 2005 18:42:27 +0200
Message-ID: <b47a630c09af1837a54c23c8b1c3c01f@implements.be> (raw)
cc ...
Begin forwarded message:
> From: Yves Vindevogel <yves.vindevogel@implements.be>
> Date: Sat 18 Jun 2005 18:18:53 CEST
> To: PFC <lists@boutiquenumerique.com>
> Subject: Re: [PERFORM] Multiple disks: RAID 5 or PG Cluster
>
> There's a basic difference between striping (raid 0) and mirroring
> (raid 1)
>
> With striping, each file is distributed over several disks, making the
> physical write faster because several disks can do the work. Same for
> reading, multiple disks return a part of the file.
> Striping can not be used for safety/backup, if one disk fails, your
> file is lost (if it is partly on that failing disk). With mirroring
> you do not lose any disk space.
>
> Mirroring is a technique for avoiding disasters when you have a disk
> failure. Every file is written twice, each time to a different disk,
> which is a mirror of the first one.
> You effectively lose half of your diskspace to that mirror. But when
> a disk fails, you don't lose anything, since you can rely on the other
> mirrored disk.
>
> Raid 10, which is the combination of that, has both. You have
> multiple disks that form your first part of the raid and you have an
> equal amount of disks for the mirror.
> On each part of the mirror, striping is used to spread the files like
> in a raid 0. This is a very costly operation. You need a minimum of
> 4 disks, and you lose 50% of your capacity.
>
> BTW: mirroring is always slower than striping.
>
> On 18 Jun 2005, at 18:00, PFC wrote:
>
>>
>>
>>> I do not know what clustering would do for you. But striping will
>>> provide a
>>> high level of assurance that each of your hard drives will process
>>> equivalent
>>> amounts of IO operations.
>>
>> I don't know what I'm talking about, but wouldn't mirorring be
>> faster than striping for random reads like you often get on a
>> database ? (ie. the reads can be dispatched to any disk) ? (or
>> course, not for writes, but if you won't use fsync, random writes
>> should be reduced no ?)
>>
>>
>>
>> ---------------------------(end of
>> broadcast)---------------------------
>> TIP 5: Have you checked our extensive FAQ?
>>
>> http://www.postgresql.org/docs/faq
>>
>>
> Met vriendelijke groeten,
> Bien à vous,
> Kind regards,
>
> Yves Vindevogel
> Implements
>
>
>
> Mail: yves.vindevogel@implements.be - Mobile: +32 (478) 80 82 91
>
> Kempische Steenweg 206 - 3500 Hasselt - Tel-Fax: +32 (11) 43 55 76
>
> Web: http://www.implements.be
>
> First they ignore you. Then they laugh at you. Then they fight you.
> Then you win.
> Mahatma Ghandi.
>
Met vriendelijke groeten,
Bien à vous,
Kind regards,
Yves Vindevogel
Implements
Mail: yves.vindevogel@implements.be - Mobile: +32 (478) 80 82 91
Kempische Steenweg 206 - 3500 Hasselt - Tel-Fax: +32 (11) 43 55 76
Web: http://www.implements.be
First they ignore you. Then they laugh at you. Then they fight you.
Then you win.
Mahatma Ghandi.
Attachments:Pasted Graphic 2.tiff (image/tiff, 5.6K) downloadview imagePasted Graphic 2.tiff (image/tiff, 5.6K) downloadview image
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: yves.vindevogel@implements.be
Subject: Re: Fwd: Multiple disks: RAID 5 or PG Cluster
In-Reply-To: <b47a630c09af1837a54c23c8b1c3c01f@implements.be>
References: <b47a630c09af1837a54c23c8b1c3c01f@implements.be>
* 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