<div dir="auto">Can the threads be categorised to do certain kinds of fops? Read/write affinitise to certain set of threads, the other metadata fops to other set of threads. So we limit the read/write threads and not the metadata threads? Also if aio is enabled in the backend the threads will not be blocked on disk IO right? <div dir="auto">All this is based on the assumption that large number of parallel read writes make the disk perf bad but not the large number of dentry and metadata ops. Is that true?</div><div dir="auto"><br></div><div dir="auto">Thanks,</div><div dir="auto">Poornima</div><br><br><div class="gmail_quote" dir="auto"><div dir="ltr">On Fri, Feb 1, 2019, 5:34 PM Emmanuel Dreyfus <<a href="mailto:manu@netbsd.org">manu@netbsd.org</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Jan 31, 2019 at 10:53:48PM -0800, Vijay Bellur wrote:<br>
> Perhaps we could throttle both aspects - number of I/O requests per disk<br>
<br>
While there it would be nice to detect and report a disk with lower than<br>
peer performance: that happen sometimes when a disk is dying, and last<br>
time I was hit by that performance problem, I had a hard time finding<br>
the culprit.<br>
<br>
-- <br>
Emmanuel Dreyfus<br>
<a href="mailto:manu@netbsd.org" target="_blank" rel="noreferrer">manu@netbsd.org</a><br>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank" rel="noreferrer">Gluster-devel@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-devel</a><br>
</blockquote></div></div>