Understanding RAID: How Performance Scales From One Disk to Eight
upstart writes in with an IRC submission for Fnord666:
Understanding RAID: How performance scales from one disk to eight:
One of the first big challenges neophyte sysadmins and data hoarding enthusiasts face is how to store more than a single disk worth of data. The short-and traditional-answer here is RAID (a Redundant Array of Inexpensive Disks), but even then there are many different RAID topologies to choose from.
Most people who implement RAID expect to get extra performance, as well as extra storage, out of all those disks. Those expectations aren't always rooted very firmly in the real world, unfortunately. But since we're all home with time for some technical projects, we hope to shed some light on how to plan for storage performance-not just the total number of gibibytes (GB) you can cram into an array.
A quick note here: Although readers will be interested in the raw numbers, we urge a stronger focus on how they relate to one another. All of our charts relate the performance of RAID arrays at sizes from two to eight disks to the performance of a single disk. If you change the model of disk, your raw numbers will change accordingly-but the relation to a single disk's performance will not for the most part.
[...] For all tests, we're using Linux kernel RAID, as implemented in the Linux kernel version 4.15, along with the ext4 filesystem. We used the --assume-clean parameter when creating our RAID arrays in order to avoid overwriting every block of the array, and we used -E lazy_itable_init=0,lazy_journal_init=0 when creating the ext4 filesystem to avoid contaminating our tests with ongoing background writes initializing the filesystem in the background.
Read more of this story at SoylentNews.