All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: waiting for sub ops
Date: Mon, 14 May 2012 08:36:37 +0200	[thread overview]
Message-ID: <4FB0A7F5.6000504@profihost.ag> (raw)
In-Reply-To: <Pine.LNX.4.64.1205132124190.29887@cobra.newdream.net>


>> 1.) th osd bench shows 150MB/s per osd
>> 2.) iperf shows constant 930Mbit/s per eth
>> 3.) when i write 16GB with dd to the ceph mount i see spikes to 450Mbit/ and
>> drops to 90kb/s for long periods of time. The overall dd speed is then
>> 40Mbit/s
> 
> We were doing some btrfs performance testing this week and seeing similar 
> bursty behavior.  (See my May 7th performance on btrfs email for some 
> out-of-context detail.)  It currently looks like the workload we're 
> presenting to the fs is resulting in non-optimal writeout, but we haven't 
> figured out yet how we can improve that or nailed down the source for the 
> burstiness.  How that some of the inktank launch stuff is out of the way 
> we'll be picking it up again and continuing to work on that this week.
> 
> If you're interested in getting involved, ping nhm in #ceph.  It would be 
> interesting to capture a block trace from your environment and see if 
> what you're seeing is what we're seeing!
Thank for your information - we've holdays in germany from thursday on
and i won't be available. So thanks for the offer.

But if you want i can provide a trace. Just tell me how i can produce one.

Thanks!

Stefan

      reply	other threads:[~2012-05-14  6:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11  7:02 waiting for sub ops Stefan Priebe - Profihost AG
2012-05-11 13:25 ` Stefan Priebe - Profihost AG
2012-05-13  0:13   ` Sage Weil
2012-05-13  0:15 ` Sage Weil
2012-05-13 18:04   ` Stefan Priebe
2012-05-14  4:28     ` Sage Weil
2012-05-14  6:36       ` Stefan Priebe - Profihost AG [this message]

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=4FB0A7F5.6000504@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@inktank.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.