[Gluster-users] Horrendously slow directory access

[james.bellinger at icecube.wisc.edu]

I am seeing something perhaps similar.  3.4.2-1, 2 servers, each with 1
brick, replicated.  A du of a local (ZFS) directory tree of 297834 files
and 525GB takes about 17 minutes.  A du of the gluster copy is still not
finished after 22 hours.  Network activity has been about 5-6KB/sec until
(I gather) du hit a directory with 22450 files, when activity jumped to
300KB/sec (200 packets/sec) for about 15-20 minutes.  If I assume that the
spike came from scanning the two largest directories, that looks like
about 8K of traffic per file, and about 5 packets.

A 3.3.2 gluster installation that we are trying to retire is not afflicted
this way.

James Bellinger

>
> Am I the only person using Gluster suffering from very slow directory
> access? It's so seriously bad that it almost makes Gluster unusable.
>
> Using NFS instead of the Fuse client masks the problem as long as the
> directories are cached but it's still hellishly slow when you first
> access them.
>
> Has there been any progress at all fixing this bug?
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1067256
>
> Cheers,
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users
>