From: Daniel Swarbrick <daniel.swarbrick@profitbricks.com>
To: ceph-devel@vger.kernel.org
Subject: Re: All-Flash Ceph cluster and journal
Date: Mon, 23 Nov 2015 19:39:28 +0100 [thread overview]
Message-ID: <n2vmh0$b9p$1@ger.gmane.org> (raw)
In-Reply-To: <3649A15A2562B54294DE14BCE5AC79120B8FA54F@FMSMSX119.amr.corp.intel.com>
Simple but clever way of ensuring that NVMe's deep queues aren't starved
of work to do. But doesn't this suggest that Ceph needs optimizing or
tuning for NVMe? Could you not have tweaked OSD parameters to ensure
more threads / IO operations in parallel and have the same effect?
On 23/11/15 18:37, Blinick, Stephen L wrote:
> This link points to a presentation we did a few weeks back where we used NVMe devices for both the data and journal. We partitioned the devices multiple times to co-locate multiple OSD's per device. The configuration data on the cluster is in the backup.
>
> http://www.slideshare.net/Inktank_Ceph/accelerating-cassandra-workloads-on-ceph-with-allflash-pcie-ssds
>
> Thanks,
>
> Stephen
>
next prev parent reply other threads:[~2015-11-23 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 11:29 All-Flash Ceph cluster and journal Mike Almateia
2015-11-19 14:34 ` Mark Nelson
2015-11-20 10:42 ` Mike Almateia
2015-11-20 10:49 ` Piotr.Dalek
2015-11-23 17:37 ` Blinick, Stephen L
2015-11-23 18:39 ` Daniel Swarbrick [this message]
2015-11-23 21:20 ` 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='n2vmh0$b9p$1@ger.gmane.org' \
--to=daniel.swarbrick@profitbricks.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 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.