Re: One client can effectively hang entire gluster array

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Thanks for responding so quickly. I'm not familiar with the codebase, so if
> you don't mind me asking, how much would that list reordering slow things
> down for, say, a queue of 1500 client machines? i.e. round-about how long of
> a client list would significantly affect latency?
>
> I only ask because we have quite a few clients and you explicitly call out
> that the queue reordering method used may have problems for lots of clients.

It's actually less about the number of clients than about the I/O queue
depth.  That's typically a pretty small number, generally proportional to
the number of storage devices and inversely proportional to their speed.
So for very large numbers of very slow devices there *might* be a problem
with the list traversals being slow, but otherwise probably not.
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel



[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux