From: Ian Holsman <lists@holsman.net>
To: nfs@lists.sourceforge.net
Subject: a nfs configuration scalability question
Date: Mon, 16 Sep 2002 12:11:59 -0700 [thread overview]
Message-ID: <3D862CFF.6080908@holsman.net> (raw)
OK..
first of all my apolagies if this is a *developer* only list.
I'm running apache2 on rh-kernel on a quad processor machine.
the docroot (where it grabs the HTML files) is being served off a
netapp750 filer.
what I'm finding is that under *any* load the runqueue goes up to ~700
and the cpu shows 100% idle. vmstat shows that all the procs are in
'blocked' state.
now.. I've tweaked the nfs mount a tiny bit to make it read only, and
have a rsize of 8k, but it didn't seem to make any difference.
$ mount
cn-sfo1-pma-filer1:/docroot on /var/httpd/online/docroot type nfs
(ro,rsize=8192,nolock,addr=10.10.112.27,addr=10.10.112.27)
the actual benchmark involves a HTTP client requesting a random URL
which reads in 10 files (9 of which are the same for each request)
on Solaris (where it is currenlty running) I can get ~1000 nfs
ops/second (mainly lookups)
so my questions:
* what tools are there for me to monitor WTF is going on (ie.. cache
hit rates inode hit rates)
* can I tweak the cache/inode size
* are there tweaks/kernel patches which will help client performance for
my type of workload
* am I being a complete dunderhead and missing something completely
obivous (if so where should I RTFM ?)
Thanks
this nfs problem is a major roadblock for me, and would appreciate ANY
pointers
Ian Holsman
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2002-09-16 19:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3D862CFF.6080908@holsman.net \
--to=lists@holsman.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox