I am seeing a pretty big perf regression with ls -l on the 3.7 branch:
https://bugzilla.redhat.com/show_bug.cgi?id=1250241
Even when running on cached results I am not seeing what I saw on 3.6:
total threads = 32
total files = 316100
98.78% of requested files processed, minimum is 70.00
20.056840 sec elapsed time
15760.209342 files/sec
In my 3.6 tests I was seeing 20k+ files per second uncached.
-b
----- Original Message -----> From: "Mathieu Chateau" <mathieu.chateau at lotp.fr>
> To: "Florian Oppermann" <gluster-users at flopwelt.de>
> Cc: "gluster-users" <gluster-users at gluster.org>
> Sent: Tuesday, August 4, 2015 4:07:13 AM
> Subject: Re: [Gluster-users] Very slow ls
>
> Sorry only read replicated in your first mail, I squashed the distributed
one
> :'(
>
>
>
> Cordialement,
> Mathieu CHATEAU
> http://www.lotp.fr
>
> 2015-08-04 9:47 GMT+02:00 Florian Oppermann < gluster-users at
flopwelt.de > :
>
>
> In my current configuration I have a distributed and replicated volume
> which is (to my understanding) similar to a raid 10.
>
> On 04.08.2015 08 :51, Mathieu Chateau wrote:
> > In a replicated scheme, it's like a raid 1 (mirror).
> > You write as slow as the slowest disk. Client will wait for all brick
> > writes confirmation.
> >
> > In this scheme, you wouldn't much more than 3 bricks.
> >
> > I think you mox up with distributed scheme, which is like a raid 0
> > stripped.
> > This one get more perf when adding bricks. But a single file is
> > present only in one brick.
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users