Bill Davidsen wrote: > Al Boldi wrote: > > The problem is that raid1 one doesn't do striped reads, but rather uses > > read-balancing per proc. Try your test with parallel reads; it should > > be faster. : : > It would be nice if reads larger than some size were considered as > candidates for multiple devices. By setting the readahead larger than > that value speed increases would be noted for sequential access.
Actually, that's what I thought for a long time too, but as Neil once pointed out, for striped reads to be efficient, each chunk should be located sequentially, as to avoid any seeks. This is only possible by introducing some offset layout, as in raid10, which infers a loss of raid1's single-disk-image compatibility. What could be feasible, is some kind of an initial burst striped readahead, which could possibly improve small reads < (readahead * nr_of_disks). Thanks! -- Al - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
