From: Jakob Oestergaard <jakob@unthought.net>
To: Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org
Subject: Re: NFS client (10x) performance regression 2.6.14.7 -> 2.6.15
Date: Mon, 3 Apr 2006 17:26:28 +0200 [thread overview]
Message-ID: <20060403152628.GA14981@unthought.net> (raw)
In-Reply-To: <20060331160426.GN9811@unthought.net>
I've run a git bisect from 2.6.14 to 2.6.15 to find what broke the NFS
client.
It seems to be the GIT patch: 24aa1fe6779eaddb3e0b1b802585dcf6faf9cc44
that introduces the problem.
Trond, it took me a lot of tries with GIT to narrow this down, because
the problem does not show up consistently. Some times nfsbench would
complete very quickly, but then a second (or third or ...) run would run
slow.
Could I ask you to try:
for i in `seq 1 100`; do time ./nfsbench; done
or something like that?
I'm looking through the patch, but to be honest the NFS cache internals
isn't really something I understand... :)
--
/ jakob
next prev parent reply other threads:[~2006-04-03 15:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 9:48 NFS client (10x) performance regression 2.6.14.7 -> 2.6.15 Jakob Oestergaard
2006-03-31 11:22 ` NFS client regression, simple test program Jakob Oestergaard
2006-03-31 12:22 ` NFS client (10x) performance regression 2.6.14.7 -> 2.6.15 Trond Myklebust
2006-03-31 12:45 ` Jakob Oestergaard
2006-03-31 13:06 ` Trond Myklebust
2006-03-31 13:21 ` Jakob Oestergaard
2006-03-31 13:44 ` Trond Myklebust
2006-03-31 14:08 ` Jakob Oestergaard
2006-03-31 14:21 ` Trond Myklebust
2006-03-31 14:35 ` Jakob Oestergaard
2006-03-31 14:49 ` Bill Rugolsky Jr.
2006-03-31 14:57 ` Jakob Oestergaard
2006-03-31 15:04 ` Bill Rugolsky Jr.
2006-03-31 15:24 ` Jakob Oestergaard
2006-03-31 16:35 ` Bill Rugolsky Jr.
2006-03-31 18:52 ` Jakob Oestergaard
2006-03-31 15:55 ` Trond Myklebust
2006-03-31 16:04 ` Jakob Oestergaard
2006-04-03 15:26 ` Jakob Oestergaard [this message]
2006-04-03 15:41 ` Trond Myklebust
2006-04-03 15:45 ` Jakob Oestergaard
2006-04-04 9:22 ` Jakob Oestergaard
2006-04-24 22:03 ` Trond Myklebust
2006-04-25 8:08 ` Jakob Oestergaard
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=20060403152628.GA14981@unthought.net \
--to=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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.