I've noticed that deleting objects from a basic k=2 m=1 erasure pool is much 
much slower than deleting a similar number of objects from a replicated size 3 
pool (so the same number of files to be deleted).   It looked like the ec pool 
object deletion was almost 20x slower.  Is there a lot more work to be done to 
delete an ec pool object?

-- Tom



> -----Original Message-----
> From: ceph-devel-ow...@vger.kernel.org [mailto:ceph-devel-
> ow...@vger.kernel.org] On Behalf Of Dalek, Piotr
> Sent: Wednesday, June 24, 2015 11:56 AM
> To: ceph-devel
> Subject: Re: deleting objects from a pool
> 
> > -----Original Message-----
> > From: ceph-devel-ow...@vger.kernel.org [mailto:ceph-devel-
> > ow...@vger.kernel.org] On Behalf Of Deneau, Tom
> > Sent: Wednesday, June 24, 2015 6:44 PM
> >
> > I have benchmarking situations where I want to leave a pool around but
> > delete a lot of objects from the pool.  Is there any really fast way to do
> that?
> > I noticed rados rmpool is fast but I don't want to remove the pool.
> >
> > I have been spawning multiple threads, each deleting a subset of the
> objects
> > (which I believe is what rados bench write does) but even that can be very
> > slow.
> 
> For now, apart from "rados -p <poolname> cleanup" (which doesn't purge the
> pool, but merely removes objects written during last benchmark run), the only
> option is by brute force:
> 
> for i in $(rados -p <poolname> ls); do (rados -p <poolname> rm $i &>/dev/null
> &); done;
> 
> There's no "purge pool" command in rados -- not yet, at least. I was thinking
> about one, but never really had time to implement one.
> 
> With best regards / Pozdrawiam
> Piotr Dałek
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to