All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mark.nelson@inktank.com>
To: Jim Schutt <jaschut@sandia.gov>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Interesting results
Date: Thu, 28 Jun 2012 17:53:28 -0500	[thread overview]
Message-ID: <4FECE068.1010701@inktank.com> (raw)
In-Reply-To: <4FECDCB0.7080406@sandia.gov>

On 06/28/2012 05:37 PM, Jim Schutt wrote:
> Hi,
>
> Lots of trouble reports go by on the list - I thought
> it would be useful to report a success.
>
> Using a patch (https://lkml.org/lkml/2012/6/28/446)
> on top of 2.5-rc4 for my OSD servers, the same kernel
> for my Linux clients, and a recent master branch
> tip (git://github.com/ceph/ceph commit 4142ac44b3f),
> I was able to sustain streaming writes from 166 linux
> clients for 2 hours:
>
> On 166 clients:
> dd conv=fdatasync if=/dev/zero of=/mnt/ceph/stripe-4M/1/zero0.`hostname
> -s` bs=4k count=65536k
>
> Elapsed time: 7274.55 seconds
> Total data: 45629732.553 MB (43515904 MiB)
> Aggregate rate: 6272.516 MB/s
>
> That kernel patch was critical; without it this test
> runs into trouble after a few minutes because the
> kernel runs into trouble looking for pages to merge
> during page compaction. Also critical were the ceph
> tunings I mentioned here:
> http://www.spinics.net/lists/ceph-devel/msg07128.html
>
> -- Jim

Nice!  Did you see much performance degradation over time?  Internally 
I've sen some slow downs (especially at smaller block sizes) as the osds 
fill up.  How many servers and how many drives?

Still, those are the kinds of numbers I like to see.  Congrats! :)

Mark

  reply	other threads:[~2012-06-28 22:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 22:37 Interesting results Jim Schutt
2012-06-28 22:53 ` Mark Nelson [this message]
2012-06-29 14:54   ` Jim Schutt
2012-07-01 19:57 ` Stefan Priebe
2012-07-02 14:04   ` Jim Schutt
2012-07-02 14:07     ` Stefan Priebe - Profihost AG
2012-07-02 14:38       ` Jim Schutt

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=4FECE068.1010701@inktank.com \
    --to=mark.nelson@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=jaschut@sandia.gov \
    /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.