Skip to contentSkip to conversation

raid io requests not parallel?

DISCUSSION Chuck Ebbert 2 participants 2 messages Jul 16, 2006

lore
Share & tools
lore
#0 lore raw

In-Reply-To: <[email protected]>

Quoted 5 lines · Jonathan Baccash
Quoted 2 lines

Each head has to service 1024 write requests (compared to just 512 read requests).

By that logic, it would take twice as long for my writes to finish. Why is it taking 4x as long in my parallel test?

Because a single read not only goes to just one disk, it is sent to the disk with the lowest expected seek time for that request. This cuts average read time in half, on average.

(See drivers/md/raid1.c::read_balance().)

Quoted 4 lines

I would expect a raid-1 write
to take about as long to write a single block as a single write to a single disk (assuming no other disk activity), because I would expect two writes to happen concurrently.

You didn't post any benchmarks showing results for single write to a single disk.

Signature · 2 lines
Chuck
 Think. Or you will be replaced with a small shell script.  --dwmw2
#1 lore raw
Quoted 5 lines

Because a single read not only goes to just one disk, it is sent to the disk with the lowest expected seek time for that request. This cuts average read time in half, on average.

(See drivers/md/raid1.c::read_balance().)

Thanks Chuck! That is making some sense, although I think I'll have to read and think about it some more before I quite understand.

Quoted 2 lines

You didn't post any benchmarks showing results for single write to a single disk.

I didn't think I could get any repeatable results for a single write, so I was trying to understand what is happening based on runs of longer writes.