linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Fuhrmann, Carsten" <carsten.fuhrmann@rwth-aachen.de>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: btrfs HDD vs SSD
Date: Thu, 5 Oct 2017 16:02:01 +0000	[thread overview]
Message-ID: <8b5db5ddf02d4832ac9abab51a5d62da@rwth-aachen.de> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1000 bytes --]

Hello,

i compared btrfs raid with mdadm raid. The mdadm raid was used with ext4 filesystem.
I used 4 SSDs and 4 HDDs in RAID0, RAID1 and RAID5. In the test I compiled the linux kernel and took the time how long it compiled + pagecache drop.
The interesting result is that btrfs is always better on the HDDs but on the SSDs mdadm is better. Do you have an explanation for that?

Furthermore I tested writing on the RAIDs. I used a tool that wrote always 1GB with different blocksizes. The filesystems had the default 4k blocksize.
For RAID5 the runtime become better and better there was no saturation even for 512k blocksize. But when I compiled the kernel with raid 5 it took the same time as it took on a btrfs no raid disk. For a RAID 1 it's fine but for RAID5 it should be faster (for RAID0 it actually is).
Can you explain those results to me?


Thank you

Carsten
 
ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±ý»k~ÏâžØ^n‡r¡ö¦zË\x1aëh™¨è­Ú&£ûàz¿äz¹Þ—ú+€Ê+zf£¢·hšˆ§~†­†Ûiÿÿïêÿ‘êçz_è®\x0fæj:+v‰¨þ)ߣøm

                 reply	other threads:[~2017-10-05 16:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8b5db5ddf02d4832ac9abab51a5d62da@rwth-aachen.de \
    --to=carsten.fuhrmann@rwth-aachen.de \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).