From: Dan Mick <dan.mick@inktank.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
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: Sat, 01 Dec 2012 16:27:29 -0800 [thread overview]
Message-ID: <50BAA071.70300@inktank.com> (raw)
In-Reply-To: <50B62580.2030301@profihost.ag>
On 11/28/2012 6:53 AM, Stefan Priebe - Profihost AG wrote:
> 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.
I did change the resize to double each time to help with that before
pushing to master, but that still seems awfully slow. You should
definitely use the
version in the mainline, though; it's better in several ways.
Are these particularly sparse images? I'm testing a "preserve
sparseness" tweak that should help
a lot if so (and save space in the cluster, obviously).
next prev parent reply other threads:[~2012-12-02 0:27 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
2012-12-02 0:27 ` Dan Mick [this message]
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=50BAA071.70300@inktank.com \
--to=dan.mick@inktank.com \
--cc=Oliver.Francke@filoo.de \
--cc=ceph-devel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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.