diff options
| author | Iustin Pop <iusty@k1024.org> | 2007-09-11 16:20:19 +0200 |
|---|---|---|
| committer | Neil Brown <neilb@suse.de> | 2007-09-11 16:20:19 +0200 |
| commit | 3dacb8902913a4c025b5beb3fb334f9d8b6dc0ce (patch) | |
| tree | 2b08469c69a4231ca794424003612a143f0eb3e7 /md.4 | |
| parent | Release 2.6.3 (diff) | |
| download | mdadm-3dacb8902913a4c025b5beb3fb334f9d8b6dc0ce.tar.xz mdadm-3dacb8902913a4c025b5beb3fb334f9d8b6dc0ce.zip | |
Explain the read-balancing algorithm for RAID1 better in md.4
From: Iustin Pop <iusty@k1024.org>
There are many questions on the mailing list about the RAID1 read
performance profile. This patch adds a new paragraph to the RAID1
section in md.4 that details what kind of speed-up one should expect
from RAID1.
Signed-off-by: Iustin Pop <iusty@k1024.org>
Diffstat (limited to 'md.4')
| -rw-r--r-- | md.4 | 7 |
1 files changed, 7 insertions, 0 deletions
@@ -168,6 +168,13 @@ All devices in a RAID1 array should be the same size. If they are not, then only the amount of space available on the smallest device is used (any extra space on other devices is wasted). +Note that the read balancing done by the driver does not make the RAID1 +performance profile be the same as for RAID0; a single stream of +sequential input will not be accelerated (e.g. a single dd), but +multiple sequential streams or a random workload will use more than one +spindle. In theory, having an N-disk RAID1 will allow N sequential +threads to read from all disks. + .SS RAID4 A RAID4 array is like a RAID0 array with an extra device for storing |