All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Almateia <mike.almateia@gmail.com>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: All-Flash Ceph cluster and journal
Date: Fri, 20 Nov 2015 13:42:30 +0300	[thread overview]
Message-ID: <564EF916.5020101@gmail.com> (raw)
In-Reply-To: <564DDDE3.9050409@redhat.com>

19-Nov-15 17:34, Mark Nelson пишет:
> This is actually the direction newstore is heading with the
> newstore_min_alloc_size so that you can configure when to write into the
> rocksdb WAL.  By default it's set to 512k, but for SSDs we will almost
> certainly want to go smaller.
>
> On 11/19/2015 05:29 AM, Mike Almateia wrote:
>> Hello.
>>
>> By now we have SSD disks with a great perfomance under O_DIRECT/O_SYNC
>> flags (and we recomended to use they for journal).
>>
>> Why in a All-Flash type Ceph clusters we still use journal and them put
>> a data into OSD?
>> Why we can't just write a data into OSD with O_DIRECT/O_SYNC flags,
>> without journal?
>>
>> Can we just switch off the journal functional for all-flash ceph
>> clusters?
>>

Thanks for answer!

By now is it resonable to use NVMe Flash for OSD on Ceph? Overpower? Is 
it possible to achive full speed NVMe Flash driver under Ceph?
--
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-11-20 10:42 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 [this message]
2015-11-20 10:49     ` Piotr.Dalek
2015-11-23 17:37       ` Blinick, Stephen L
2015-11-23 18:39         ` Daniel Swarbrick
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=564EF916.5020101@gmail.com \
    --to=mike.almateia@gmail.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.