All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mnelson@redhat.com>
To: "Deneau, Tom" <tom.deneau@amd.com>, Sage Weil <sage@newdream.net>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: rados bench single instance vs. multiple instances
Date: Wed, 13 May 2015 11:16:35 -0500	[thread overview]
Message-ID: <555378E3.4000309@redhat.com> (raw)
In-Reply-To: <BC97738F8E7C8742BABED7F06FB9DF91664428FA@SATLEXDAG01.amd.com>

On 05/13/2015 10:05 AM, Deneau, Tom wrote:
>
>
>> -----Original Message-----
>> From: Sage Weil [mailto:sage@newdream.net]
>> Sent: Monday, May 11, 2015 12:04 PM
>> To: Deneau, Tom
>> Cc: ceph-devel
>> Subject: Re: rados bench single instance vs. multiple instances
>>
>> On Mon, 11 May 2015, Deneau, Tom wrote:
>>> I have noticed the following while running rados bench seq read tests
>>> with a 40M object size
>>>
>>>      single rados bench, 4 concurrent ops,                     bandwidth =
>> 190 MB/s
>>>      4 copies of rados bench, 1 concurrent op each,  aggregate
>>> bandwidth = 310 MB/s
>>>
>>> and in fact the single rados bench seems limited to 190, no matter how many
>> concurrent ops.
>>>
>>> I don't see this kind of behavior with a 4M object size.
>>>
>>> (The above are with caches dropped on the osd targets)
>>>
>>> It doesn't seem to be related to the total number of bytes being
>>> processed by the single because if I don't drop the caches, both the
>>> single rados bench and the 4-copy rados bench get much higher numbers
>>> (600 vs. 900) but still the single rados bench appears limited, no matter
>> how many concurrent ops are used.
>>>
>>> Is there kind of throttling going on by design here?
>>
>> It might be the librados throttles:
>>
>> OPTION(objecter_inflight_op_bytes, OPT_U64, 1024*1024*100) // max in-flight
>> data (both directions)
>> OPTION(objecter_inflight_ops, OPT_U64, 1024)               // max in-flight
>> ios
>>
>> IIRC these only affect librados.. which would include 'rados bench'.
>>
>> sage
>>
>
> Just a follow-up that changing the limits of the two options mentioned above
> did indeed solve my problem.

Yay!  I suspect max bytes more so than max ops?


Mark

>
> Also, my naïve understanding of the architecture was that things like RBD and RGW were
> layered on librados as shown in http://ceph.com/docs/master/architecture/.  So wouldn't these
> throttles apply to those stacks as well?
>
> -- Tom Deneau
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-05-13 16:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 14:18 rados bench single instance vs. multiple instances Deneau, Tom
2015-05-11 14:23 ` Mark Nelson
2015-05-11 16:27   ` Deneau, Tom
2015-05-11 17:03 ` Sage Weil
2015-05-11 17:13   ` Mark Nelson
2015-05-11 17:15   ` Deneau, Tom
2015-05-11 17:18     ` Gregory Farnum
2015-05-11 17:25       ` Deneau, Tom
2015-05-11 17:27         ` Gregory Farnum
2015-05-13 15:05   ` Deneau, Tom
2015-05-13 16:16     ` Mark Nelson [this message]
2015-05-13 17:13       ` Deneau, Tom
2015-05-13 17:01     ` Sage Weil

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=555378E3.4000309@redhat.com \
    --to=mnelson@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@newdream.net \
    --cc=tom.deneau@amd.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.