linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Tripathy <jonnyt-Nf8S+5hNwl710XsdtD+oqA@public.gmane.org>
To: "linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Expected Behavior
Date: Thu, 30 Aug 2012 08:21:30 +0100	[thread overview]
Message-ID: <503F147A.10101@abpni.co.uk> (raw)
In-Reply-To: <503F132E.6060305-Nf8S+5hNwl710XsdtD+oqA@public.gmane.org>

On 30/08/2012 08:15, Jonathan Tripathy wrote:
> Hi There,
>
> On my WIndows DomU (Xen VM) which is running on a LV which is using 
> bcache (against two SSD in MDRAID1 and a MD-RAID10 spindle array), I 
> ran an IOMeter test for about 2 hours (with 30 workers and a io depth 
> of 256). This was a very heavy workload (Got an average iops of about 
> 6.5k). After I stopped the test, I then went back to fio on my Linux 
> Xen Host (Dom0). The random write performance isn't as good as it was 
> before I started the IOMeter test. It used to be about 25k and now 
> showed about 7k iops. I assumed that maybe this was due to the fact 
> that bcache was writing out dirty data to the spindles so the SSD was 
> busy.
>
> However, this morning, after the spindles have calmed down, 
> performance of fio is still not great (still about 7k).
>
> Is there something wrong here? What is expected behavior?
>
> Thanks
>
BTW, I can confirm that this isn't an SSD issue, as I have a partition 
on the SSD that I kept seperate from bcache and I'm getting excellent 
(about 28k) iops performance there.

It's as if after the heavy workload I did with IOMeter, bcache has 
somehow throttled the writeback cache?

Any help is appreciated.

  parent reply	other threads:[~2012-08-30  7:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-30  7:15 Expected Behavior Jonathan Tripathy
     [not found] ` <503F132E.6060305-Nf8S+5hNwl710XsdtD+oqA@public.gmane.org>
2012-08-30  7:21   ` Jonathan Tripathy [this message]
     [not found]     ` <503F147A.10101-Nf8S+5hNwl710XsdtD+oqA@public.gmane.org>
2012-08-30  7:26       ` Jonathan Tripathy
     [not found]         ` <503F15A9.5020000-Nf8S+5hNwl710XsdtD+oqA@public.gmane.org>
2012-08-30  7:34           ` Jonathan Tripathy
2012-08-30 12:18       ` Jonathan Tripathy
     [not found]         ` <239802233aa1dabc37f60b293d2941c9-Nf8S+5hNwl710XsdtD+oqA@public.gmane.org>
2012-08-30 21:28           ` Kent Overstreet
     [not found]             ` <20120830212841.GB14247-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2012-08-30 22:59               ` Jonathan Tripathy
     [not found]                 ` <503FF05B.1040506-Nf8S+5hNwl710XsdtD+oqA@public.gmane.org>
2012-08-31  1:10                   ` Kent Overstreet
2012-08-31  3:47                   ` James Harper
     [not found]                     ` <6035A0D088A63A46850C3988ED045A4B29A7D49D-mzsoxcrO4/2UD0RQwgcqbDSf8X3wrgjD@public.gmane.org>
2012-08-31 12:36                       ` Jonathan Tripathy
     [not found]                         ` <a7955ba43dfd9792245545eeb8c54e55-Nf8S+5hNwl710XsdtD+oqA@public.gmane.org>
2012-08-31 12:41                           ` Jonathan Tripathy
     [not found]                             ` <151f74230aeb6825d9b8b633881d5e6c-Nf8S+5hNwl710XsdtD+oqA@public.gmane.org>
2012-09-01 12:47                               ` Jonathan Tripathy
     [not found]                                 ` <504203F8.4000302-Nf8S+5hNwl710XsdtD+oqA@public.gmane.org>
2012-09-03  0:37                                   ` Kent Overstreet
     [not found]                                     ` <20120903003750.GA20060-jC9Py7bek1znysI04z7BkA@public.gmane.org>
2012-09-03  8:30                                       ` Jonathan Tripathy
     [not found]                                         ` <fd31f46503030cb2f09c50453971f618-Nf8S+5hNwl710XsdtD+oqA@public.gmane.org>
2012-09-04  3:46                                           ` Kent Overstreet

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=503F147A.10101@abpni.co.uk \
    --to=jonnyt-nf8s+5hnwl710xsdtd+oqa@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;
as well as URLs for NNTP newsgroup(s).