public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Ng <ppng-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Poor performance with bcache write-back mode
Date: Mon, 3 Jun 2013 21:44:59 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130603T233345-71@post.gmane.org> (raw)
In-Reply-To: 20130529004058.GF2291@google.com

Kent Overstreet <koverstreet@...> writes:

> 
> On Thu, May 16, 2013 at 02:51:46PM -0700, Patrick Ng wrote:
> > Hi all,
> > 
> > I have installed Linux kernel 3.9.2 in my Fedora 18.  When I ran FIO in 
bcache write-through mode, the
> performance was good, but running a similar test in bcache write-back 
mode, I got very poor performance.
> > Did I miss any options when setting the write-back mode?
> > 
> > Environment
> > ===========
> > 500G backing store at /dev/sdb1
> > 150G SSD at /dev/sdc1
> > 
> > Write-through mode
> > ==================
> > make-bcache -B /dev/sdb1 -C /dev/sdc1
> > echo /dev/sdb1 > /sys/fs/bcache/register
> > echo /dev/sdc1 > /sys/fs/bcache/register
> > mkfs.ext4 /dev/bcache0
> > mount /dev/bcache0 /mnt/bcache
> > 
> > 
> > Running FIO with random, 100% read, iosize=4096, queue depth=16
> > the result is approx. 65k IOPS
> > 
> > 
> > Write-backe mode (setup is almost the same as write-through except the 
extra step at the end "echo
> writeback ...")
> > ================
> > make-bcache -B /dev/sdb1 -C /dev/sdc1
> > echo /dev/sdb1 > /sys/fs/bcache/register
> > echo /dev/sdc1 > /sys/fs/bcache/register
> > mkfs.ext4 /dev/bcache0
> > mount /dev/bcache0 /mnt/bcache
> > echo writeback > /sys/block/bcache0/bcache/cache_mode
> > 
> > Running FIO with random, 100% read, iosize=4096, queue depth=16
> > the result is approx. 12k IOPS
> > 
> > Running FIO with random, 80% read 20% write, iosize=4096, queue depth=16
> > the result is approx. 2k IOPS
> 
> You're probably getting bit by the congested bypass - try setting
> congested_read_threshold_us and congested_write_threshold_us both to 0.
> 
> I wish there was a better solution to the congestion bypass stuff, it's
> a hard problem...
> 

Hi Kent, thank you for responding to my question.

I have tried setting both congested_read_threshold_us and 
congested_write_threshold_us to zero.

The result of FIO random 100% read test in WriteBack mode has improved and 
the IOPS is as good as in WriteThur mode.

The result of FIO random 80% read 20% write remain the same with no 
improvement.

It appears that the option does not help on the WRITE?

Thanks,
Patrick

  reply	other threads:[~2013-06-03 21:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16 21:51 Poor performance with bcache write-back mode Patrick Ng
     [not found] ` <1368741106.62060.YahooMailNeo-QseONlJJzSFal3a5i+KC+JEhsgyP+Z75VpNB7YpNyf8@public.gmane.org>
2013-05-17  6:28   ` Robert Frånlund
2013-05-29  0:40   ` Kent Overstreet
2013-06-03 21:44     ` Patrick Ng [this message]
     [not found] ` <CA+gjuN7E2B+71BiCexm7HjDGzJMBuCdbGxhvD8YHU6-u6TyKkg@mail.gmail.com>
     [not found]   ` <CA+gjuN7E2B+71BiCexm7HjDGzJMBuCdbGxhvD8YHU6-u6TyKkg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-17 20:13     ` Patrick Ng
2013-05-17 20:50       ` Gabriel de Perthuis

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=loom.20130603T233345-71@post.gmane.org \
    --to=ppng-/e1597as9lqavxtiumwx3w@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