CEPH filesystem development
 help / color / mirror / Atom feed
From: Mark Nelson <mark.nelson@inktank.com>
To: David Blundell <David.Blundell@100percentit.com>
Cc: Alexandre DERUMIER <aderumier@odiso.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Slow request warnings on 0.48
Date: Thu, 05 Jul 2012 14:49:17 -0500	[thread overview]
Message-ID: <4FF5EFBD.1060603@inktank.com> (raw)
In-Reply-To: <45F11B42CB5830479EF0E56A27F4E68D7F4E54@exchange1.ad.100it.net>

On 07/05/2012 01:43 PM, David Blundell wrote:
>> Hi David and Alexandre,
>>
>> Does this only happen with random writes or also sequential writes?  If it
>> happens with sequential writes as well, does it happen with rados bench?
>>
>> --
>> Mark Nelson
>> Performance Engineer
>> Inktank
>
> Hi Mark,
>
> I just ran "rados -p data bench 60 write -t 16" and a few dd tests with no problems at all so at the moment it looks like only random IO triggers the slow writes.
>
> Please do let me know if there are any other tests that I can do to help track down the cause.
>
> David

Thanks David!  We've got some people internally taking a look at this. 
I'll let you guys know if there is anything else we need!

Thanks,
Mark

-- 
Mark Nelson
Performance Engineer
Inktank

  reply	other threads:[~2012-07-05 19:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-04 16:53 Slow request warnings on 0.48 David Blundell
2012-07-04 16:58 ` Alexandre DERUMIER
2012-07-04 18:59   ` Gregory Farnum
2012-07-04 22:03     ` David Blundell
2012-07-05 17:58   ` Mark Nelson
2012-07-05 18:16     ` David Blundell
2012-07-05 18:33     ` Alexandre DERUMIER
2012-07-05 18:43     ` David Blundell
2012-07-05 19:49       ` Mark Nelson [this message]
2012-07-05 20:21         ` Samuel Just
2012-07-05 22:15           ` David Blundell
  -- strict thread matches above, loose matches on Subject: below --
2012-07-19 10:48 Matthew Richardson

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=4FF5EFBD.1060603@inktank.com \
    --to=mark.nelson@inktank.com \
    --cc=David.Blundell@100percentit.com \
    --cc=aderumier@odiso.com \
    --cc=ceph-devel@vger.kernel.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