From: Vivek Goyal <vgoyal@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: virtio-fs@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Virtio-fs] [PATCH 1/1] virtiofsd: Do not use a thread pool by default
Date: Tue, 16 Feb 2021 13:04:29 -0500 [thread overview]
Message-ID: <20210216180429.GC3196@redhat.com> (raw)
In-Reply-To: <YCwHDvMDDYMy+4de@work-vm>
On Tue, Feb 16, 2021 at 05:55:26PM +0000, Dr. David Alan Gilbert wrote:
> * Vivek Goyal (vgoyal@redhat.com) wrote:
> > Currently we created a thread pool (With 64 max threads per pool) for
> > each virtqueue. We hoped that this will provide us with better scalability
> > and performance.
> >
> > But in practice, we are getting better numbers in most of the cases
> > when we don't create a thread pool at all and a single thread per
> > virtqueue receives the request and processes it.
> >
> > Hence, I am proposing that we switch to no thread pool by default
> > (equivalent of --thread-pool-size=0). This will provide out of
> > box better performance to most of the users. In fact other users
> > have confirmed that not using a thread pool gives them better
> > numbers. So why not use this as default. It can be changed when
> > somebody can fix the issues with thread pool performance.
> >
> > Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
>
> OK, lets try it - I still worry it really means we're missing something
> silly about them, you'd really think eventually the threads should help.
Agreed. Once we figure out what are we missing with threading and
start getting better performance with multi-threading, we will need
to make thread pool default again.
Vivek
>
>
>
> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>
> > ---
> > tools/virtiofsd/fuse_lowlevel.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tools/virtiofsd/fuse_lowlevel.c b/tools/virtiofsd/fuse_lowlevel.c
> > index e94b71110b..fbdf62ee9b 100644
> > --- a/tools/virtiofsd/fuse_lowlevel.c
> > +++ b/tools/virtiofsd/fuse_lowlevel.c
> > @@ -18,7 +18,7 @@
> >
> > #include <sys/file.h>
> >
> > -#define THREAD_POOL_SIZE 64
> > +#define THREAD_POOL_SIZE 0
> >
> > #define OFFSET_MAX 0x7fffffffffffffffLL
> >
> > --
> > 2.25.4
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>
> _______________________________________________
> Virtio-fs mailing list
> Virtio-fs@listman.redhat.com
> https://listman.redhat.com/mailman/listinfo/virtio-fs
prev parent reply other threads:[~2021-02-16 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 18:27 [PATCH 0/1] virtiofsd: Do not use a thread pool by default Vivek Goyal
2021-02-10 18:27 ` [PATCH 1/1] " Vivek Goyal
2021-02-16 17:55 ` [Virtio-fs] " Dr. David Alan Gilbert
2021-02-16 18:04 ` Vivek Goyal [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210216180429.GC3196@redhat.com \
--to=vgoyal@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virtio-fs@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).