All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mnelson@redhat.com>
To: "Blinick, Stephen L" <stephen.l.blinick@intel.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
	Samuel Just <sjust@redhat.com>, Kyle Bader <kbader@redhat.com>,
	Somnath Roy <Somnath.Roy@sandisk.com>
Subject: Re: Increasing # Shards vs multi-OSDs per device
Date: Wed, 11 Nov 2015 15:01:37 -0600	[thread overview]
Message-ID: <5643ACB1.6040102@redhat.com> (raw)
In-Reply-To: <3649A15A2562B54294DE14BCE5AC79120B8ED66F@ORSMSX160.amr.corp.intel.com>

Hi Stephen,

That's about what I expected to see, other than the write performance 
drop with more shards.  We clearly still have some room for improvement.

Good job doing the testing!

Mark

On 11/11/2015 02:57 PM, Blinick, Stephen L wrote:
> Sorry about the microphone issues in the performance meeting today today.   This is a followup to the 11/4 performance meeting where we discussed increasing the worker thread count in the OSD's vs making multiple OSD's (and partitions/filesystems) per device.     We did the high level experiment and have some results which I threw into a ppt/pdf, and shared them here:
>
> http://www.docdroid.net/UbmvGnH/increasing-shards-vs-multiple-osds.pdf.html
>
> Doing 20-shard OSD's vs 4 OSD's per device with default 5 shards yielded about half of the performance improvement for random 4k reads.  For writes performance is actually worse than just 1 OSD per device and the default # of shards.  The throttles should be large enough for the 20-shard use case as they are 10x the defaults, although if you see anything we missed let us know.
>
> I had the cluster moved to Infernalis release (with JEMalloc) yesterday, so hopefully we'll have some early results on the same 5-node cluster soon.
>
> Thanks,
>
> Stephen
>
>

  reply	other threads:[~2015-11-11 21:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 20:57 Increasing # Shards vs multi-OSDs per device Blinick, Stephen L
2015-11-11 21:01 ` Mark Nelson [this message]
2015-11-11 21:59 ` Somnath Roy
     [not found] ` <CAH0kLp8pQW=Ainqm5w7yfBgzSj2AKum125CiqJ+r5k=cvR53Ug@mail.gmail.com>
2015-11-11 22:44   ` Blinick, Stephen L
2015-11-11 23:29     ` Robert LeBlanc
2015-11-12 22:50       ` Blinick, Stephen L

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=5643ACB1.6040102@redhat.com \
    --to=mnelson@redhat.com \
    --cc=Somnath.Roy@sandisk.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=kbader@redhat.com \
    --cc=sjust@redhat.com \
    --cc=stephen.l.blinick@intel.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.