From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: nfs@lists.sourceforge.net
Subject: slow performance -- how to diagnose
Date: Wed, 19 Apr 2006 16:14:05 -0400 [thread overview]
Message-ID: <1145477646.12854.152.camel@pc> (raw)
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
I'm experiencing some slow performance that I have done some initial
diagnosis as per http://nfs.sourceforge.net/nfs-howto/performance.html
but not sure where to go from here.
I have tried both UDP and TCP and in fact UDP performance seems to be
slightly worse.
The connection between a client and the server is gige and seems to
perform pretty close to such using ttcp:
ttcp-t: 819200000 bytes in 7.368 real seconds = 848.299 Mbit/sec +++
ttcp-t: 819200000 bytes in 7.01 real seconds = 891.19 Mbit/sec +++
The first is from client to server and the second server to client.
Both seem reasonable.
The speed of the disk on the server using a simple dd test:
# time dd if=/dev/zero of=file bs=1M count=4000
4000+0 records in
4000+0 records out
real 2m28.756s
user 0m0.024s
sys 0m17.141s
(1024*1024*4000)/148.7/(1024*1024)*8 == 26.899 MB/sec == 215.192Mbit/s
But from an NFS client...
# rsh client5 "(cd $(pwd);time dd if=/dev/zero of=file bs=1M count=1000)"
1000+0 records in
1000+0 records out
real 1m21.036s
user 0m0.006s
sys 0m1.982s
(1024*1024*1000)/81.036/(1024*1024) == 12.340 MB/sec
Any ideas where to look?
b.
--
My other computer is your Microsoft Windows server.
Brian J. Murrell
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
reply other threads:[~2006-04-19 20:14 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=1145477646.12854.152.camel@pc \
--to=brian@interlinx.bc.ca \
--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