All of lore.kernel.org
 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 performance with small blocksize on SSD
Date: Sun, 24 Sep 2017 13:24:30 +0000	[thread overview]
Message-ID: <3321b3c199da4d378bbfa3dbac3c4059@rwth-aachen.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 745 bytes --]

Hello,

i run a few performance tests comparing mdadm, hardware raid and the btrfs raid. I noticed that the performance for small blocksizes (2k) is very bad on SSD in general and on HDD for sequential writing.
I wonder about that result, because you say on the wiki that btrfs is very effective for small files. 

I attached my results from raid 1 random write HDD (rH1), SSD (rS1) and from sequential write HDD (sH1), SSD (sS1)

Hopefully you have an explanation for that.

raid@raid-PowerEdge-T630:~$ uname -a
Linux raid-PowerEdge-T630 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11 14:07:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
raid@raid-PowerEdge-T630:~$ btrfs --version
btrfs-progs v4.4


best regards

Carsten


[-- Attachment #2: rH1.png --]
[-- Type: image/png, Size: 9075 bytes --]

[-- Attachment #3: rS1.png --]
[-- Type: image/png, Size: 8625 bytes --]

[-- Attachment #4: sH1.png --]
[-- Type: image/png, Size: 8582 bytes --]

[-- Attachment #5: sS1.png --]
[-- Type: image/png, Size: 9438 bytes --]

             reply	other threads:[~2017-09-24 13:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-24 13:24 Fuhrmann, Carsten [this message]
2017-09-24 13:40 ` Btrfs performance with small blocksize on SSD Qu Wenruo
2017-09-24 13:53   ` AW: " Fuhrmann, Carsten
2017-09-24 14:10     ` Qu Wenruo
2017-09-24 14:22       ` AW: " Fuhrmann, Carsten
2017-09-24 16:43     ` Andrei Borzenkov
2017-09-24 20:39       ` Kai Krakow
2017-09-25  7:04       ` AW: AW: " Fuhrmann, Carsten
2017-09-25  8:36         ` Kai Krakow
2017-09-26 20:33 ` Peter Grandi

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=3321b3c199da4d378bbfa3dbac3c4059@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.