[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Virtio-fs] tools/virtiofs: Multi threading seems to hurt performanc
From: |
Dr. David Alan Gilbert |
Subject: |
Re: [Virtio-fs] tools/virtiofs: Multi threading seems to hurt performance |
Date: |
Fri, 25 Sep 2020 12:35:12 +0100 |
User-agent: |
Mutt/1.14.6 (2020-07-11) |
* Chirantan Ekbote (chirantan@chromium.org) wrote:
> On Sat, Sep 19, 2020 at 6:36 AM Vivek Goyal <vgoyal@redhat.com> wrote:
> >
> > Hi All,
> >
> > virtiofsd default thread pool size is 64. To me it feels that in most of
> > the cases thread pool size 1 performs better than thread pool size 64.
> >
> > I ran virtiofs-tests.
> >
> > https://github.com/rhvgoyal/virtiofs-tests
> >
> > And here are the comparision results. To me it seems that by default
> > we should switch to 1 thread (Till we can figure out how to make
> > multi thread performance better even when single process is doing
> > I/O in client).
> >
>
> FWIW, we've observed the same behavior in crosvm. Using a thread pool
> for the virtiofs server consistently gave us worse performance than
> using a single thread.
Interesting; so it's not just us doing something silly!
It does feel like you *should* be able to get some benefit from multiple
threads; so I guess some more investigation needed at some time.
Dave
> Chirantan
>
> _______________________________________________
> Virtio-fs mailing list
> Virtio-fs@redhat.com
> https://www.redhat.com/mailman/listinfo/virtio-fs
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
- Re: tools/virtiofs: Multi threading seems to hurt performance, (continued)
Re: tools/virtiofs: Multi threading seems to hurt performance, Vivek Goyal, 2020/09/21
Re: [Virtio-fs] tools/virtiofs: Multi threading seems to hurt performance, Chirantan Ekbote, 2020/09/23