[end of last message was truncated, here is the rest]
Next I tried 2560 for stripe_cache_size, since that is the 512KB x 5
stripe width.
random
random
KB reclen write rewrite read reread read write
4194304 64 201919 141025 139386 134252 7421
13327
4194304 128 194337 123513 237911 237901 13002
22758
4194304 256 181426 142159 256929 252772 21986
30099
4194304 512 183168 175516 234975 234090 32614
40375
4194304 1024 169051 163818 220393 233060 54738
58653
4194304 2048 173281 141452 237993 234881 95969
77678
4194304 4096 162690 142784 208838 211268 90016
96876
4194304 8192 151361 125652 197484 197278 124009
112708
4194304 16384 138971 106200 183750 183659 135876
121704
So the sequential reads at 200+ MB/s look okay (although I do not
understand the huge throughput variability with record size), but the
writes are not as high as with 16MB stripe cache. This may be the
setting that I decide to stick with, but I would like to understand
what is going on.
Why did increasing the stripe cache from 256 KB to 16 MB decrease the
sequential read speeds?
Also, let me know what other parameters I should tune during my optimizations.
--
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
