[Gluster-devel] I/O performance

[Poornima Gurusiddaiah]

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?
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?

Thanks,
Poornima


On Fri, Feb 1, 2019, 5:34 PM Emmanuel Dreyfus <manu at netbsd.org wrote:

> On Thu, Jan 31, 2019 at 10:53:48PM -0800, Vijay Bellur wrote:
> > Perhaps we could throttle both aspects - number of I/O requests per disk
>
> While there it would be nice to detect and report  a disk with lower than
> peer performance: that happen sometimes when a disk is dying, and last
> time I was hit by that performance problem, I had a hard time finding
> the culprit.
>
> --
> Emmanuel Dreyfus
> manu at netbsd.org
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20190201/dc5d20b7/attachment.html>