All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amon Ott <a.ott@m-privacy.de>
To: ceph-devel@vger.kernel.org
Subject: Re: Integration work
Date: Wed, 29 Aug 2012 09:06:47 +0200	[thread overview]
Message-ID: <201208290906.48788.a.ott@m-privacy.de> (raw)
In-Reply-To: <CANLRBoyP6TmjA8BPgXR4DE1O6ux_U+AAoU3i2jFW6yjU415KyA@mail.gmail.com>

On Tuesday 28 August 2012 you wrote:
> On Tue, Aug 28, 2012 at 11:51 AM, Dieter Kasper <d.kasper@kabelmail.de> 
wrote:
> > Hi Ross,
> >
> > focusing on core stability and feature expansion for RBD was the right
> > appoach in the past and I feel you have reached an adequate maturity
> > level here.
> >
> > Performance enhancements - especially to reduce the latency of a single
> > IO / increase IOPS - and a stronger engagement on the CephFS client would
> > be very much appreciated. A stable and fast CephFS client would allow an
> > efficient integration with - (clustered) NFS (v3 and v4)
> > - (clustered) Samba v4
>
> +1 to CephFS being worked on. Things like the multi-mds being improved
> upon would be amazing.

Stable CephFS is what we need, too - many concurrent write accesses from 
multiple clients with a real file system underneath. However, most stability 
problems we have had so far were crashes in the daemons, not the Linux 
kernel. Great for me would be some solution to what we call the Domino 
effect - one daemon crashes, the next takes over, crashes at the same place 
(same data...), until the whole cluster is down. There will always be bugs, 
but they should not kill the whole cluster.

In our tests, single MDS was no real bottleneck, it was only lacking 
stability. I have not tested the newest releases, so it might be better now. 
Improved performance with many small files being written concurrently would 
be great, but CephFS has been getting significantly faster over the last year 
and performance is being worked on all the time.

Amon Ott
-- 
Dr. Amon Ott
m-privacy GmbH           Tel: +49 30 24342334
Am Köllnischen Park 1    Fax: +49 30 99296856
10179 Berlin             http://www.m-privacy.de

Amtsgericht Charlottenburg, HRB 84946

Geschäftsführer:
 Dipl.-Kfm. Holger Maczkowsky,
 Roman Maczkowsky

GnuPG-Key-ID: 0x2DD3A649
--
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:[~2012-08-29  7:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-28 18:12 Integration work Ross Turk
2012-08-28 18:32 ` Plaetinck, Dieter
2012-08-28 21:03   ` Florian Haas
2012-08-28 21:15     ` Tommi Virtanen
2012-08-28 21:20       ` Josh Durgin
2012-08-30 14:00         ` João Eduardo Luís
2012-08-28 18:51 ` Dieter Kasper
2012-08-28 18:57   ` Smart Weblications GmbH - Florian Wiessner
2012-08-28 20:05     ` Dieter Kasper
2012-08-28 20:46   ` Tren Blackburn
2012-08-29  7:06     ` Amon Ott [this message]
2012-08-29  8:20 ` Sylvain Munaut
2012-08-29  9:53   ` Wido den Hollander
2012-08-29 12:35     ` Sylvain Munaut
2012-08-29 13:40       ` Wido den Hollander
2012-08-29 13:43         ` Tommi Virtanen
2012-08-29 15:19           ` Joseph Glanville
2012-08-29 15:19           ` Joseph Glanville
2012-09-01  6:02 ` Ryan Nicholson
2012-09-04 15:52   ` Tommi Virtanen

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=201208290906.48788.a.ott@m-privacy.de \
    --to=a.ott@m-privacy.de \
    --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.