From: Olaf Kirch <okir@suse.de>
To: Patrice Seyed <apseyed@bu.edu>
Cc: 'Joshua Baker-LePain' <jlb17@duke.edu>, nfs@lists.sourceforge.net
Subject: Re: ReasmFails increases / NFS performance on Linux Cluster
Date: Tue, 17 Aug 2004 10:05:23 +0200 [thread overview]
Message-ID: <20040817080523.GA17099@suse.de> (raw)
In-Reply-To: <005f01c483d4$b6fa9f40$6701a8c0@psyche1>
On Mon, Aug 16, 2004 at 05:05:09PM -0400, Patrice Seyed wrote:
> You don't have enough threads. That 2nd number (after the number of
> threads) should be as close to zero as possible -- that's the number of
> times all threads have been busy when a request came in. IIRC, you have
> plenty of memory on the server -- crank up the number of threads and you
> should see some difference.
Not necessarily. We're talking about nfsd threads hung in a COMMIT call -
these can take over a second, and will block all WRITE calls to the same
file for the entire duration. So a single client doing write-behind can
easily tie up 8 or more server threads.
Olaf
--
Olaf Kirch | The Hardware Gods hate me.
okir@suse.de |
---------------+
-------------------------------------------------------
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-17 8:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1BwYLA-0004on-C0@sc8-sf-list2.sourceforge.net>
2004-08-16 12:54 ` ReasmFails increases / NFS performance on Linux Cluster Joshua Baker-LePain
2004-08-16 21:05 ` Patrice Seyed
2004-08-17 8:05 ` Olaf Kirch [this message]
2004-08-14 7:46 Patrice Seyed
2004-08-14 9:23 ` Olaf Kirch
2004-08-15 21:52 ` Patrice Seyed
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=20040817080523.GA17099@suse.de \
--to=okir@suse.de \
--cc=apseyed@bu.edu \
--cc=jlb17@duke.edu \
--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.