On Sat, Oct 15, 2016 at 1:36 AM, Heller, Chris <cheller@xxxxxxxxxx> wrote: > Just a thought, but since a directory tree is a first class item in cephfs, could the wire protocol be extended with an “recursive delete” operation, specifically for cases like this? In principle yes, but the problem is that the POSIX filesystem interface doesn't have a recursive delete operation (we just see a series of individual unlinks), so the complicated part would be making the client clever enough to notice when a series of unlink operations appear to be traversing a particular directory, and batching them up until all files in a directory are unlinked, and then finally sending a recursive unlink message to the server. John > > On 10/14/16, 4:16 PM, "Gregory Farnum" <gfarnum@xxxxxxxxxx> wrote: > > On Fri, Oct 14, 2016 at 1:11 PM, Heller, Chris <cheller@xxxxxxxxxx> wrote: > > Ok. Since I’m running through the Hadoop/ceph api, there is no syscall boundary so there is a simple place to improve the throughput here. Good to know, I’ll work on a patch… > > Ah yeah, if you're in whatever they call the recursive tree delete > function you can unroll that loop a whole bunch. I forget where the > boundary is so you may need to go play with the JNI code; not sure. > -Greg > > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |