From: NeilBrown <neilb@suse.de>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/7] Add RCU-walk support to NFS.
Date: Wed, 23 Jul 2014 17:14:08 +1000 [thread overview]
Message-ID: <20140723171408.481387f1@notabene.brown> (raw)
In-Reply-To: <CAHQdGtSmLH6GJ6iw0dyKmpVvvvcuK9-+T2KcJu0+_S8CsgtqOA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1838 bytes --]
On Sun, 13 Jul 2014 22:39:34 -0400 Trond Myklebust
<trond.myklebust@primarydata.com> wrote:
> > I'm certainly happy to try beating on it a bit hard, and can see if I can get
> > access to an 80-core machine that I had a brief play with a while back and do
> > some more testing there.
>
> As I said, it's not required for merging, but would definitely be an
> interesting test in order to see how it affects NFS performance in
> general. If you have access to a good test setup with an interesting
> workload, then I'd love to see the results of a "before vs after"
> comparison using nfsometer.
>
I managed to get access to a big machine for a while so I ran nfsometer.
Seemed to run quite well but there are a couple of little issues I might
mention separately.
I didn't let iozone_direct complete because it was taking *forever*.
The results are at http://neil.brown.name/nfsometer_results/
I cannot find a good summary page...
I tested three kernels on the same 80-core (160 if you count hyperthreads)
machine:
A v3.12 that was installed,
a vanilla 3.16-rc5,
and the 3.16-rc5 with my patches.
Some numbers look good, some look strange.
Can you (or someone) have a look?
I also ran my compile-test and graphed some results, which I attach.
This is just 3 kernels, 3.16-rc5 with and without my patches.
I tested both v3 and v4.
I ran the "make" command with "-j" values from 4 to 80 in steps of 4.
The runs lots of compiles of a trivial file but has a very long list of
include directories which are all on NFS and all empty. So there are lots of
attempts to open non-existent files, and the non-existence is cached early.
As you see, with the "-rcu" very performance is enormously better. Without
my patches, more concurrency means worse performance.
Thanks,
NeilBrown
[-- Attachment #1.2: make-times.png --]
[-- Type: image/png, Size: 5948 bytes --]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2014-07-23 7:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 1:28 [PATCH 0/7] Add RCU-walk support to NFS NeilBrown
2014-07-14 1:28 ` [PATCH 2/7] NFS: prepare for RCU-walk support but pushing tests later in code NeilBrown
2014-07-14 1:28 ` [PATCH 6/7] NFS: teach nfs_lookup_verify_inode to handle LOOKUP_RCU NeilBrown
2014-07-14 1:28 ` [PATCH 3/7] sunrpc/auth: allow lockless (rcu) lookup of credential cache NeilBrown
2014-07-14 1:28 ` [PATCH 4/7] NFS: support RCU_WALK in nfs_permission() NeilBrown
2014-07-14 1:28 ` [PATCH 1/7] NFS: nfs4_lookup_revalidate: only evaluate parent if it will be used NeilBrown
2014-07-15 16:56 ` Christoph Hellwig
2014-07-14 1:28 ` [PATCH 5/7] NFS: teach nfs_neg_need_reval to understand LOOKUP_RCU NeilBrown
2014-07-14 1:28 ` [PATCH 7/7] NFS: allow lockless access to access_cache NeilBrown
2014-07-14 2:00 ` [PATCH 0/7] Add RCU-walk support to NFS Trond Myklebust
2014-07-14 2:25 ` NeilBrown
2014-07-14 2:39 ` Trond Myklebust
2014-07-23 7:14 ` NeilBrown [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=20140723171408.481387f1@notabene.brown \
--to=neilb@suse.de \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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 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.