From: Gabriel de Perthuis <g2p.code-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Very poor performances with the bcache-for-upstream branch
Date: Thu, 2 May 2013 05:50:54 +0000 (UTC) [thread overview]
Message-ID: <klsuru$l60$2@ger.gmane.org> (raw)
In-Reply-To: CA+XuAnJO4BCE0yj0i_CZ_iQvDj56FHwFZH302XrisD45P5R3Tw@mail.gmail.com
> 2. I have setup an LVM above bcache, and /dev/sda4 is the only cache
> partition. The whole thing was setup with:
>
> make-bcache -B /dev/sda4 -C /dev/sdb
>
> the LVM is "inside" /dev/sda4
> 3. I am using fio as a benchmark, have setup writeback
> # cat /sys/block/bcache0/bcache/writeback_running
> 1
> and I think I have followed every hints I could found about performance tuning.
> Yet, when running the ssd fio test suite on a file on partition that
> is not "cached", I am obtaining the following figures:
> seq-read: iops=29156
> rand-read: iops=291
> seq-write: iops=22355
> rand-write: iops=260
>
> Running it on a cached file system I'm obtaining:
> seq-read: iops=22196
> rand-read: iops=330
> seq-write: iops=15864
> rand-write: iops=387
>
> What am I missing ?
Outside of the make-bcache, none of the commands you give in the thread
prove that the cache is assembled (it's actually possible to have
writeback_running = 1 with a detached bdev, though that's a bug in my
opinion). What does `ls -d /sys/fs/bcache/*/bdev*` show?
next prev parent reply other threads:[~2013-05-02 5:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 15:43 Very poor performances with the bcache-for-upstream branch Leslie Basmid
[not found] ` <CA+XuAnJO4BCE0yj0i_CZ_iQvDj56FHwFZH302XrisD45P5R3Tw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-29 17:52 ` Kent Overstreet
[not found] ` <CAC7rs0t4uKx37i7pxMoMQgVeUT6spDeridfdC+R6mqLbf1dwug-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-30 3:46 ` block activity stats matthew patton
[not found] ` <1367293610.13617.YahooMailClassic-XYahOdtEMNn35Xbc4wGBzZOW+3bF1jUfVpNB7YpNyf8@public.gmane.org>
2013-04-30 20:31 ` Kent Overstreet
[not found] ` <20130430203134.GI9931-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2013-05-01 1:10 ` Jason Warr
2013-05-01 13:30 ` Very poor performances with the bcache-for-upstream branch Leslie Basmid
[not found] ` <CA+XuAnK4nNOG_tSuuteDThbj5L+5xmDsxQLfrHj314z1fr+bUA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-01 15:36 ` matthew patton
[not found] ` <1367422594.24900.YahooMailClassic-XYahOdtEMNm2Y7dhQGSVAJOW+3bF1jUfVpNB7YpNyf8@public.gmane.org>
2013-05-01 16:56 ` Leslie Basmid
[not found] ` <CA+XuAn+Z-gxkfeE8D-A1-EJ4_QEBUqPJYfc40jevkJFbMzQ+Rw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-01 18:56 ` Kent Overstreet
[not found] ` <20130501185638.GB4057-jC9Py7bek1znysI04z7BkA@public.gmane.org>
2013-05-01 19:50 ` Leslie Basmid
2013-05-02 5:50 ` Gabriel de Perthuis [this message]
2013-05-02 16:13 ` Leslie Basmid
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='klsuru$l60$2@ger.gmane.org' \
--to=g2p.code-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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