All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Dan Mick <dan.mick@inktank.com>
Cc: Oliver Francke <Oliver.Francke@filoo.de>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: rbd STDIN import does not work / wip-rbd-export-stdout
Date: Wed, 28 Nov 2012 15:53:52 +0100	[thread overview]
Message-ID: <50B62580.2030301@profihost.ag> (raw)
In-Reply-To: <50B484FF.9070500@profihost.ag>

Hi Dan,

thanks for your update / new import-export branch.

The import seems to work now. What i'm wondering is that it is really slow.

I see around 10% CPU Usage on importing host (host where rbd import is 
started) and just 4MB every 2s raising Data on ceph. This means 40GB 
took around 5-6 hours.

Night this be due to he size update? 4MB every 2s looks like the stripe 
size.

Greets,
Stefan

  parent reply	other threads:[~2012-11-28 14:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26 13:20 rbd STDIN import does not work / wip-rbd-export-stdout Stefan Priebe - Profihost AG
2012-11-26 13:29 ` Oliver Francke
2012-11-26 13:35   ` Stefan Priebe - Profihost AG
2012-11-26 17:34     ` Dan Mick
2012-11-26 19:35       ` Stefan Priebe - Profihost AG
2012-11-26 20:00         ` Dan Mick
2012-11-27  9:16           ` Stefan Priebe - Profihost AG
2012-11-27 22:50             ` Josh Durgin
2012-11-28  8:09               ` Stefan Priebe - Profihost AG
2012-11-28 18:51                 ` Josh Durgin
2012-11-29 10:26                   ` Stefan Priebe - Profihost AG
2012-11-28 14:53             ` Stefan Priebe - Profihost AG [this message]
2012-12-02  0:27               ` Dan Mick
2012-12-01 20:23             ` Stefan Priebe
2012-12-02  0:28               ` Dan Mick

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=50B62580.2030301@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=Oliver.Francke@filoo.de \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dan.mick@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.