On Tue, Feb 15, 2011 at 09:50:42AM +1100, NeilBrown wrote:
> > I experimented a bit with write-mostly and write-behind and found that
> > write-mostly provides a very significant benefit (see below) but
> > write-behind seems to have no effect whatsoever.
>
> The use-case where write-behind can be expected to have an effect is when the
> throughput is low enough to be well within the capacity of all devices, but
> the latency of the write-behind device is higher than desired.
> write-behind will allow that high latency to be hidden (as long as the
> throughput limit is not exceeded).
>
> I suspect your tests did not test for low latency in a low-throughput
> scenario.
I thought they did. "High latency" was, in my case, caused by the high seek
times (compared to the SSD) of the spinning disks. Throughput-wise, they
certainly could have kept up (their sequential read/write performance even
exceeds that of the SSD).
But maybe I misunderstand how write-behind works. I thought/hoped it would
commit writes to the fast drive(s) and mark affected areas dirty in the
intent map, then lazily sync the dirty areas over to the slow disk(s).
What does it actually do? md(4) isn't very forthcoming, and the wiki has no
relevant hits either.
Thanks.
--
Andras Korn <korn at elan.rulez.org>
Baroque: (def.) When you are out of Monet.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
