From: bfields@fieldses.org (J. Bruce Fields)
To: jhopper@Safe-mail.net
Cc: linux-nfs@vger.kernel.org
Subject: Re: extremely slow v4 performance on gigabit link
Date: Wed, 5 Aug 2015 14:24:00 -0400 [thread overview]
Message-ID: <20150805182400.GA18809@fieldses.org> (raw)
In-Reply-To: <N1B-heRnt8zOCE@Safe-mail.net>
On Wed, Aug 05, 2015 at 07:13:58AM -0400, jhopper@Safe-mail.net wrote:
> I have a very slow (less than 1MB/s) performance with nfsv4 TCP,
How are you measuring this?
> rsize/wsize have no effect, server is a kernel 3.19 x86 100hz no
> preempt exporting async nfsv4 TCP on nfs-utils 1.2.7,
The "async" export option isn't normally recommended, though it's
unlikely to have anything to do with this problem.
> client is a
> kernel 4.1.3 x64 1000hz full preempt with nfs-utils 1.3.2 , physical
> link is 1 gigabit full duplex, I mounted a few cifs shares to check,
> the cifs shares are working at 30 MB/s and higher
>
> is it possible that preempt has an effect on NFS performance ? does
> timeslice have effect on performance ?
I think those are unlikely to be relevant.
--b.
next prev parent reply other threads:[~2015-08-05 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 11:13 extremely slow v4 performance on gigabit link jhopper
2015-08-05 18:24 ` J. Bruce Fields [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-06 14:48 jhopper
2015-08-10 15:23 ` J. Bruce Fields
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=20150805182400.GA18809@fieldses.org \
--to=bfields@fieldses.org \
--cc=jhopper@Safe-mail.net \
--cc=linux-nfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.