From: Guido Winkelmann <guido-ceph@thisisnotatest.de>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: "rbd rm image" slow with big images ?
Date: Fri, 01 Jun 2012 15:51:19 +0200 [thread overview]
Message-ID: <2839159.qIikQGmnXF@pc10> (raw)
In-Reply-To: <Pine.LNX.4.64.1205311118150.28422@cobra.newdream.net>
Am Donnerstag, 31. Mai 2012, 11:19:44 schrieben Sie:
> On Thu, 31 May 2012, Wido den Hollander wrote:
> > Hi,
> >
> > > Is it the normal behaviour ? Maybe some xfs tuning could help ?
> >
> > It's in the nature of RBD.
>
> Yes.
>
> That said, the current implementation is also stupid: it's doing a single
> io at a time. #2256 (next sprint) will parallelize this to make it go
> much faster (probably an order of magnitude?).
Will it speed up copy operations as well? Those are a lot more important in
practice... A delete operation I can usually just fire off and leave running
in the background, but if I'm running a copy operation, there's usually
something else waiting (like starting a virtual server that's waiting for its
disk) that cannot proceed until the copy is actually finished.
On another note, it looks to me (correct me if I'm wrong) like rbd copy
operations always involve copying all the data objects from the source volume
to the machine on which the rbd command is running, and then back to the
cluster, even if that machine isn't even part of the cluster. Are there any
plans to streamline this?
Regards,
Guido
next prev parent reply other threads:[~2012-06-01 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6bb4f478-37c9-460d-8a0d-698e32dcf08d@mailpro>
2012-05-31 7:12 ` "rbd rm image" slow with big images ? Alexandre DERUMIER
2012-05-31 18:15 ` Wido den Hollander
2012-05-31 18:16 ` Stefan Priebe
2012-05-31 19:39 ` Wido den Hollander
2012-05-31 18:19 ` Sage Weil
2012-06-01 4:38 ` Alexandre DERUMIER
2012-06-01 13:51 ` Guido Winkelmann [this message]
2012-06-01 20:33 ` Wido den Hollander
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=2839159.qIikQGmnXF@pc10 \
--to=guido-ceph@thisisnotatest.de \
--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.