From: Mark Nelson <mark.nelson@inktank.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: Sage Weil <sage@inktank.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"hch@infradead.org >> Christoph Hellwig" <hch@infradead.org>
Subject: Re: FS / Kernel question choosing the correct kernel version
Date: Tue, 26 Jun 2012 11:59:49 -0500 [thread overview]
Message-ID: <4FE9EA85.9030809@inktank.com> (raw)
In-Reply-To: <4FE9E6CB.8080803@profihost.ag>
On 06/26/2012 11:43 AM, Stefan Priebe wrote:
> Am 26.06.2012 18:29, schrieb Mark Nelson:
>> On 06/26/2012 11:15 AM, Stefan Priebe wrote:
>> Hi Stefan,
>>
>> If you can, it would be really interesting to see the blktrace results
>> during these tests for both xfs and btrfs. blktrace is in the ubuntu
>> repositories and can be run quite easily from the command line during
>> your test.
>
> Sure any special parameters? I have 4 SSDs per OSD Server.
>
> Or just blktrace -o file?
>
> Stefan
For each device you run it on you'll get one file per core. There may
be some performance impact if you run blktrace on every device per node.
If your data is well distributed, even a trace for one OSD (per test)
would be interesting.
so blktrace -o <outfile prefix> -d <device> where device is your first
OSD or something. If you can do it for both btrfs and xfs and maybe run
each test for a couple of minutes that might be enough.
Mark
next prev parent reply other threads:[~2012-06-26 17:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 18:26 FS / Kernel question choosing the correct kernel version Stefan Priebe
2012-06-25 22:11 ` Sage Weil
2012-06-26 8:14 ` Christoph Hellwig
2012-06-26 8:26 ` Stefan Priebe
2012-06-26 9:39 ` Stefan Priebe
2012-06-26 16:02 ` Sage Weil
2012-06-26 9:07 ` Stefan Priebe
2012-06-26 16:15 ` Stefan Priebe
2012-06-26 16:29 ` Mark Nelson
2012-06-26 16:43 ` Stefan Priebe
2012-06-26 16:59 ` Mark Nelson [this message]
2012-06-26 17:49 ` Stefan Priebe
2012-06-26 17:49 ` Stefan Priebe
2012-06-26 18:04 ` Stefan Priebe
2012-06-26 20:07 ` Mark Nelson
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=4FE9EA85.9030809@inktank.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=hch@infradead.org \
--cc=s.priebe@profihost.ag \
--cc=sage@inktank.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 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.