From: "Wendy Cheng" <wendy.cheng@falconstor.com>
To: <nfs@lists.sourceforge.net>
Subject: NFS Read Performance
Date: Sat, 22 Mar 2003 11:26:31 -0500 [thread overview]
Message-ID: <002301c2f08f$cd30c430$19103942@tamarac> (raw)
we're conducting SPEC SFS97 benchmark runs
to evaluate Linux performance as NFS file servers.
It is observed that an unusual high percentage of
benchmark time was spent in "read" operation.
A sampled workload consisting of 18% of read
consumes 63% of total benchmark time. Did this
problem get analyzed before (or even better :)-
is there a patch) ? We're on 2.4.19 kernel- NFS
V3 - UDP, with EXT3 as local file system.
Thanks in advance.
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2003-03-22 16:26 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='002301c2f08f$cd30c430$19103942@tamarac' \
--to=wendy.cheng@falconstor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox