Announcement
Collapse
No announcement yet.
Btrfs RAID 0/1 Benchmarks On The Linux 4.1 Kernel
Collapse
X
-
Looking forward to the RAID 10 tests as I suspect that's what almost everyone using BTRFS RAID today is using including myself (6x 2Tb SATA drives).
-
Originally posted by duby229 View PostTheoretically RAID1 can be as fast as all disks combined for sequential reads as long as the RAID controller supports proper load balancing.
In that respect, btrfs is so much better than block based raid1 because btrfs knows which copy is not corrupt.
Btrfs raid works on "file level" (extent level is more like it I guess), so on a 2 disk raid 1 the layout on one disk can be totally different from the other disk.
So as soon as BTRFS is really trustworthy stable, I will use it on bare disks, and scrap my md-raid. But for now md-raid is proven technology and fast too.
Leave a comment:
-
Originally posted by toyotabedzrock View PostAnd since when does anyone use four drives for raid 1?
Originally posted by toyotabedzrock View PostDid he mean to test 0+1?
Leave a comment:
-
Recently I've built a NAS (MicroServer N40L, running Fedora 21) for my colleague, with 5 disks. 4*2TB WD Green form a Btrfs RAID5.
I've tired the write to Btrfs RAID5, the write speed (using both 4K and 1M block size) ranged from 31x MB/s ~ 330 MB/s the guy was pretty happy about the result.
Screenshot -> https://flic.kr/p/sbZEVx
Leave a comment:
-
I'd really like to see some benchmarks analyzing the performance of btrfs with snapshots (since that's why most people use it). Something like:
1. write data
2. snapshot
3. read & write, modifying ~5% of the data
4. repeat from 2.
My anecdotal experience suggests that it slows down massively for the common use case, but it'd be nice to see some verification of this.
Leave a comment:
-
Originally posted by duby229 View PostTheoretically RAID1 can be as fast as all disks combined for sequential reads as long as the RAID controller supports proper load balancing. I'm not sure about how btrfs implements load balancing. It rarely happens though because most reads aren't very sequential. You'll only get maximum performance when reading large sequential files and most linux systems are comprised of thousands of very tiny files where access latency becomes the bottleneck.
And since when does anyone use four drives for raid 1? Did he mean to test 0+1?
Leave a comment:
-
Originally posted by stiiixy View Post
Curiously, does compressing the small-files sections (like the system directories), particularly if they're text, help reduce the this access? I know it used to in to a degree on the old spinning discs. But nowadays, all this newandangled stuff...
Speaking about compressing small files, I keep a squashfs filesystem mounted just for that purpose. It gets synced every night so the next days filesystem is last nights image. It really does help improve performance when accessing many small files.
Leave a comment:
-
Originally posted by duby229 View PostTheoretically RAID1 can be as fast as all disks combined for sequential reads as long as the RAID controller supports proper load balancing. I'm not sure about how btrfs implements load balancing. It rarely happens though because most reads aren't very sequential. You'll only get maximum performance when reading large sequential files and most linux systems are comprised of thousands of very tiny files where access latency becomes the bottleneck.
Leave a comment:
-
Nice benchmarks!
Mind including the "single JBOD" config in the tests, too?
Leave a comment:
-
Theoretically RAID1 can be as fast as all disks combined for sequential reads as long as the RAID controller supports proper load balancing. I'm not sure about how btrfs implements load balancing. It rarely happens though because most reads aren't very sequential. You'll only get maximum performance when reading large sequential files and most linux systems are comprised of thousands of very tiny files where access latency becomes the bottleneck.
Leave a comment:
Leave a comment: