From: Wido den Hollander <wido@widodh.nl>
To: Guido Winkelmann <guido-ceph@thisisnotatest.de>
Cc: ceph-devel@vger.kernel.org
Subject: Re: "rbd rm image" slow with big images ?
Date: Fri, 01 Jun 2012 22:33:34 +0200 [thread overview]
Message-ID: <4FC9271E.6010809@widodh.nl> (raw)
In-Reply-To: <2839159.qIikQGmnXF@pc10>
Hi,
On 06/01/2012 03:51 PM, Guido Winkelmann wrote:
> 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.
>
#2256 is only about parallelizing deletions:
http://tracker.newdream.net/issues/2256
I don't see a feature request in the tracker for parallelizing a copy,
but we can always create that one :)
> 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?
>
You are running the rbd command on that client, so that client will read
the object and write them again as new RADOS objects.
What you are asking is a "cluster-side" clone of a volume, correct?
There is working on-going for layering, where you have one "golden
image" with multiple childs. With that you can achieve what you want,
but it's not always desired in every situation.
There has been talking about promoting a child to a fresh volume, that
would be the same as the cloning you are talking about. I don't know the
status of that.
Wido
> Regards,
> Guido
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-06-01 20:33 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
2012-06-01 20:33 ` Wido den Hollander [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=4FC9271E.6010809@widodh.nl \
--to=wido@widodh.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=guido-ceph@thisisnotatest.de \
/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.