From: | "Ruth Ivimey-Cook" <Ruth(dot)Ivimey-Cook(at)ivimey(dot)org> |
---|---|
To: | "'Guy'" <bugzilla(at)watkins-home(dot)com>, "'Michael Tokarev'" <mjt(at)tls(dot)msk(dot)ru>, "'Arshavir Grigorian'" <ag(at)m-cam(dot)com> |
Cc: | <linux-raid(at)vger(dot)kernel(dot)org>, <pgsql-performance(at)postgresql(dot)org> |
Subject: | Effect of Stripe Size (was Postgres on RAID5) |
Date: | 2005-03-15 16:17:55 |
Message-ID: | 20050315161838.B4FC2568C4@svr1.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Folks,
> You said:
> "If your write size is smaller than chunk_size*N (N = number
> of data blocks in a stripe), in order to calculate correct
> parity you have to read data from the remaining drives."
>
> Neil explained it in this message:
> http://marc.theaimsgroup.com/?l=linux-raid&m=108682190730593&w=2
Having read that and the recent posts:
Has anyone done any performance checks on the md code to determine what, if
any, effect the stripe size has on performance? One might suppose the variables
would be stripe size, file size and read vs write. Possibly number of drives in
array, too.
Reason for asking:
When I set up my raid5 array, I chose a stripe of 256K, on the grounds that a
large number of the files on the drive are multi-megabytes (fairly evenly in
the 20MB - 100MB range) and I supposed that a large stripe would speed things
up for those files. Was I right?
Regards,
Ruth
From | Date | Subject | |
---|---|---|---|
Next Message | PFC | 2005-03-15 17:17:31 | Re: [PERFORM] Avoiding tuple construction/deconstruction during joining |
Previous Message | Stef | 2005-03-15 15:23:45 | Slow loads when indexes added. |