From: "Priyank Patel" <pkpatel.lists@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.26.3 kernel - progressive slowdown over NFS
Date: Thu, 11 Sep 2008 13:17:55 -0700 [thread overview]
Message-ID: <f4e12c70809111317x221ab6bcmcb8bdbf2e0074f83@mail.gmail.com> (raw)
In-Reply-To: <f4e12c70809091747rd58165ahaa6594a35752c6ef@mail.gmail.com>
Resending. Any pointers to other lists or more specific information
which might be required ?
Thanks,
-P
PS : Please cc me on the response.
On Tue, Sep 9, 2008 at 5:47 PM, Priyank Patel <pkpatel.lists@gmail.com> wrote:
> Hi,
>
>
> We have a simple python program which keeps running a C loop to lstat
> NFS mounted directories. We are seeing some weird behavior w.r.t. the
> run-time of this program on 2.6.26.3 kernel vs 2.6.24 kernel.
>
> The run-time of the following code increases over time on the 2.6.26.3
> kernel, whereas remains flat (as expected) on the 2.6.24 kernel.
> [See attached graphs - B1.jpg and B2.jpg] Once the 2.6.26.3 machine
> gets into this state, we need to restart the box to get back to
> reasonable run-times. Is this a known issue ?
>
> Setup :
>
> Machine A (2.6.26) : exports NFS directory - /a/baz contains 10,000
> directories bar0 ... bar9999
> /a/baz *(rw,sync,no_root_squash,no_all_squash,subtree_check)
>
> Machine B1 (2.6.26.3) : mounts NFS dir RO from A - graph B1.jpg
> 10.x.x.x:/a/baz on /baz type nfs
> (ro,vers=3,rsize=4096,wsize=4096,namlen=255,hard,nointr,nolock,proto=udp,timeo=11,retrans=2,sec=sys,mountproto=udp,addr=10.x.x.x)
>
> Machine B2 (2.6.24) : mounts NFS dir RO from A - graph B2.jpg
> 10.x.x.x:/a/baz on /baz type nfs
> (ro,vers=3,rsize=4096,wsize=4096,hard,nointr,nolock,proto=udp,timeo=11,retrans=2,sec=sys,addr=10.x.x.x)
>
> Repro :
>
> B1 and B2, run the following python program :
> {{{
> #!/usr/bin/env python
>
> import os
> import sys
> import time
>
> while True:
> t1 = time.time()
> rv = os.system("/a.out 10000 >& /dev/null") # lstat the 10000
> directories mounted via NFS
> t2 = time.time()
> print >> sys.stderr, "%.3f" % (t2 - t1), rv
> }}}
>
> where a.out is the following C code :
>
> {{{
> #include <stdio.h>
> #include <stdlib.h>
> #include <sys/types.h>
> #include <sys/stat.h>
> #include <unistd.h>
>
> int main(int argc, char **argv)
> {
> int i, n = atoi(argv[1]);
> char filename[64];
> struct stat statbuf;
>
> for (i = 0; i < n; i++) {
> sprintf(filename, "/baz/bar%d", i);
> lstat(filename, &statbuf);
> }
>
> printf("done\n");
> return 0;
> }
> }}}
>
> Attachments :
>
> B1.jpg and B2.jpg - runtimes on the 2 client machines -
> X-axis : iteration number
> Y-axis : run-time
>
> Config files : - for the machines B1, B2 and A
>
> b1.2.6.26.3.config
> b2.2.6.24.config
> a.2.6.26.config
>
>
> - P
>
next prev parent reply other threads:[~2008-09-11 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 0:47 2.6.26.3 kernel - progressive slowdown over NFS Priyank Patel
2008-09-11 20:17 ` Priyank Patel [this message]
2008-12-09 16:31 ` David Flynn
2008-12-10 21:26 ` Andrew Morton
2008-12-10 0:38 ` Fwd: " Ray Lee
2008-12-10 1:06 ` Trond Myklebust
2008-12-10 1:12 ` Ray Lee
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=f4e12c70809111317x221ab6bcmcb8bdbf2e0074f83@mail.gmail.com \
--to=pkpatel.lists@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox