From: Ian Thurlbeck <ian@stams.strath.ac.uk>
To: Steve Dickson <SteveD@redhat.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Strange delays on NFS server
Date: Mon, 16 Aug 2004 13:40:38 +0100 [thread overview]
Message-ID: <4120AB46.1080606@stams.strath.ac.uk> (raw)
In-Reply-To: <411CD601.1080308@RedHat.com>
Steve Dickson wrote:
>
>
> Ian Thurlbeck wrote:
>
>> PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND
>> 6365 root 16 0 1244 1244 880 R 0.9 0.2 0:15 0 top
>> 156 root 15 0 0 0 0 DW 0.0 0.0 25:45 0 kjournald
>> 2021 root 15 0 0 0 0 DW 0.0 0.0 17:38 0 nfsd
>> 2037 root 15 0 0 0 0 DW 0.0 0.0 17:51 0 nfsd
>> 2042 root 15 0 0 0 0 DW 0.0 0.0 17:07 0 nfsd
>> 2044 root 15 0 0 0 0 DW 0.0 0.0 16:44 0 nfsd
>>
>> And then the bdflush process joins in and the number of nfsd processes
>> grows, then shrinks back, and finally they all disappear.
>>
> Hmm... this is kinda what I expected... nfsd is waiting on the local
> filesystem....
> Would it be nice if nfsd would know how to speak aio... but back to
> reality.....
> What happens if you double/triple (assuming you have enough memory) the
> number nfsd
> that are started? does it help or hurt? My guess is it probably will not
> make a difference
I bumped the nfsd's up to 64 (from 32) and subjectively the problem gets
worse. I then reduced them to 16 and things are a bit better...
Would changing some of the bdflush settings help at all?
Thanks
Ian
--
Ian Thurlbeck http://www.stams.strath.ac.uk/
Statistics and Modelling Science, University of Strathclyde
Livingstone Tower, 26 Richmond Street, Glasgow, UK, G1 1XH
Tel: +44 (0)141 548 3667 Fax: +44 (0)141 552 2079
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-08-16 12:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 10:55 Strange delays on NFS server Ian Thurlbeck
2004-08-11 11:58 ` Olaf Kirch
2004-08-11 12:58 ` Steve Dickson
2004-08-11 16:08 ` Ian Thurlbeck
2004-08-11 16:41 ` Olaf Kirch
2004-08-11 16:53 ` Phy Prabab
2004-08-11 16:57 ` Christoph Hellwig
2004-08-11 19:42 ` Norman Weathers
2004-08-12 8:04 ` Ian Thurlbeck
2004-08-12 15:15 ` Ian Thurlbeck
2004-08-13 14:53 ` Steve Dickson
2004-08-16 12:40 ` Ian Thurlbeck [this message]
[not found] ` <20040816131434.GL3510@suse.de>
[not found] ` <4120C8D5.3040606@stams.strath.ac.uk>
[not found] ` <20040816145435.GQ3510@suse.de>
[not found] ` <4124CD95.7020007@stams.strath.ac.uk>
[not found] ` <20040820095854.GC23176@suse.de>
2004-08-24 9:48 ` Ian Thurlbeck
2004-08-24 10:27 ` Jan Bruvoll
2004-08-25 2:02 ` Greg Banks
2004-08-25 8:40 ` Ian Thurlbeck
2004-08-25 10:02 ` Greg Banks
2004-08-25 10:36 ` Ian Thurlbeck
2004-08-24 11:07 ` Neil Brown
2004-08-24 14:22 ` Ian Thurlbeck
2004-08-24 23:54 ` Neil Brown
2004-08-26 11:01 ` Strange delays on NFS server (with piccies) Ian Thurlbeck
2004-08-27 1:22 ` Neil Brown
2004-08-27 4:10 ` Greg Banks
2004-08-11 19:07 ` Strange delays on NFS server Steve Dickson
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=4120AB46.1080606@stams.strath.ac.uk \
--to=ian@stams.strath.ac.uk \
--cc=SteveD@redhat.com \
--cc=nfs@lists.sourceforge.net \
/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.