From: Stefan Priebe <s.priebe@profihost.ag>
To: Sage Weil <sage@inktank.com>
Cc: Mark Nelson <mark.nelson@inktank.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: RBD speed vs threads
Date: Fri, 15 Jun 2012 22:29:25 +0200 [thread overview]
Message-ID: <4FDB9B25.1080707@profihost.ag> (raw)
In-Reply-To: <Pine.LNX.4.64.1206150931440.4551@cobra.newdream.net>
Am 15.06.2012 18:33, schrieb Sage Weil:
> The one other thing worth mentioning here is that "thread" is really a
> misnomer. Rados bench is actually dispatching it's IO asynchronously from
> a single thread, and the -t option is really controlling the number of
> IO's in flight. That is more or less what you get if you have N threads
> doing a single synchronous IO each, which is why the option is called
> that.
THX
Stefan
next prev parent reply other threads:[~2012-06-15 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 5:56 RBD speed vs threads Stefan Priebe - Profihost AG
2012-06-15 12:03 ` Mark Nelson
2012-06-15 16:33 ` Sage Weil
2012-06-15 20:29 ` Stefan Priebe [this message]
2012-06-15 20:28 ` Stefan Priebe
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=4FDB9B25.1080707@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=mark.nelson@inktank.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox