<div dir="ltr">Hi Patrick,<div><br></div><div style="">Is it possible to test out whether the patch fixes your issue? There is nothing like validation from user experiencing the problem first hand.</div><div style=""><br></div><div style="">regards,</div><div style="">Raghavendra</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 12, 2016 at 10:40 PM, Jeff Darcy <span dir="ltr"><<a href="mailto:jdarcy@redhat.com" target="_blank">jdarcy@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> Thanks for responding so quickly. I'm not familiar with the codebase, so if<br>
> you don't mind me asking, how much would that list reordering slow things<br>
> down for, say, a queue of 1500 client machines? i.e. round-about how long of<br>
> a client list would significantly affect latency?<br>
><br>
> I only ask because we have quite a few clients and you explicitly call out<br>
> that the queue reordering method used may have problems for lots of clients.<br>
<br>
</span>It's actually less about the number of clients than about the I/O queue<br>
depth. That's typically a pretty small number, generally proportional to<br>
the number of storage devices and inversely proportional to their speed.<br>
So for very large numbers of very slow devices there *might* be a problem<br>
with the list traversals being slow, but otherwise probably not.<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Raghavendra G<br></div>
</div>