linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: "G. Richard Bellamy" <rbellamy@pteradigm.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs and iostat - how do I measure the live performance of my  btrsf filesystems?
Date: Wed, 06 Aug 2014 01:39:22 +0200	[thread overview]
Message-ID: <40ee87d5d8b24230774bf28018ceb289@admin.virtall.com> (raw)
In-Reply-To: <CADw2B2MgvUt_bL11ZOAZjyk+R2pmM5JbLVjmgqoXBHSTEypMqw@mail.gmail.com>

On 2014-08-06 00:06, G. Richard Bellamy wrote:
> On Tue, Aug 5, 2014 at 7:14 AM, Tomasz Chmielewski <mangoo@wpkg.org> 
> wrote:
>> Simple iostat won't give you meaningful live performance stats.
>> 
>> You can combine it i.e. like below:
>> 
>> iostat -x 1
>> iostat -mx 1
>> iostat -m 1
> 
> Thanks for the pointer about viewing the extended stats, and showing
> them in MB rather than kB.
> 
> Maybe I'm missing something here. I'm failing to see how adding those
> additional stats helps me get meaningful throughput information for a
> multi-device btrfs volume.

Well you won't see an aggregate, but you will see individual device 
statistics with "1" at the end of iostat arguments (meaning, dump the 
stats every second).


-- 
Tomasz Chmielewski
http://www.sslrack.com


  reply	other threads:[~2014-08-05 23:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 14:14 btrfs and iostat - how do I measure the live performance of my btrsf filesystems? Tomasz Chmielewski
2014-08-05 22:06 ` G. Richard Bellamy
2014-08-05 23:39   ` Tomasz Chmielewski [this message]
2014-08-22 21:36     ` G. Richard Bellamy
2014-08-23  3:24       ` Duncan
2014-08-23  4:13         ` G. Richard Bellamy
  -- strict thread matches above, loose matches on Subject: below --
2014-08-04 23:01 G. Richard Bellamy

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=40ee87d5d8b24230774bf28018ceb289@admin.virtall.com \
    --to=mangoo@wpkg.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rbellamy@pteradigm.com \
    /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).