Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!kddlab!titcca!cc.titech.ac.jp!necom830!mohta
From: mohta@necom830.cc.titech.ac.jp (Masataka Ohta)
Newsgroups: comp.dcom.lans
Subject: Re: FDDI Performance
Message-ID: <7185@titcce.cc.titech.ac.jp>
Date: 6 Feb 91 07:13:01 GMT
References: <1991Feb1.175751.13639@relay.nswc.navy.mil> <7178@titcce.cc.titech.ac.jp> <83979@sgi.sgi.com>
Sender: news@cc.titech.ac.jp
Organization: Tokyo Institute of Technology
Lines: 57

In article <83979@sgi.sgi.com>
	vjs@rhyolite.wpd.sgi.com (Vernon Schryver) writes:

>> NFS speed is about 1MB/sec for writing and 2MB/sec for reading.

>How was NFS speed measured?  Nfsstone or one of the other benchmarks?

Just read/write large files.

>What, if any, compensation for client and server cache policies and mechanisms
>was there?

For reading, the read file is completely in the buffer cache at the
server, but the client could have no cache because the read file is
created on the server and new to the client.

For writing, according to the NFS specification, writing must be somewhat
synchronous, so forget about caching.

>Is the UDP speed quoted above the value reported by the transimitter or by
>the receiver?

Of course, 40Mbps is observed on both side. I know what is UDP.

I can understand that the figure has astonished you. But, please,
don't assume I am an idiot and make a rather lengthy post. You could
have used mail.

Also, you should have considered more and should have noticed that
2MB/sec (equivalent to 16Mbps) NFS read speed support my observation
of UDP speed.

By the way, I also performed nhfsstone with varying load from 10 to 210.

nhfsstone -l 10: 490 sec 5022 calls 10.24 calls/sec 7.49 msec/call
nhfsstone -l 20: 245 sec 5019 calls 20.48 calls/sec 7.13 msec/call
nhfsstone -l 30: 163 sec 5043 calls 30.93 calls/sec 8.03 msec/call
nhfsstone -l 40: 123 sec 5025 calls 40.85 calls/sec 8.72 msec/call
nhfsstone -l 50: 99 sec 5017 calls 50.67 calls/sec 9.03 msec/call
nhfsstone -l 60: 81 sec 5033 calls 62.13 calls/sec 11.64 msec/call
nhfsstone -l 70: 70 sec 5022 calls 71.74 calls/sec 11.55 msec/call
nhfsstone -l 80: 61 sec 5011 calls 82.14 calls/sec 11.14 msec/call
nhfsstone -l 90: 54 sec 5011 calls 92.79 calls/sec 11.98 msec/call
nhfsstone -l 100: 49 sec 5016 calls 102.36 calls/sec 13.52 msec/call
nhfsstone -l 110: 44 sec 5032 calls 114.36 calls/sec 14.48 msec/call
nhfsstone -l 120: 41 sec 5016 calls 122.34 calls/sec 17.43 msec/call
nhfsstone -l 130: 37 sec 5012 calls 135.45 calls/sec 18.22 msec/call
nhfsstone -l 140: 35 sec 5020 calls 143.42 calls/sec 25.37 msec/call
nhfsstone -l 150: 34 sec 5019 calls 147.61 calls/sec 27.23 msec/call
nhfsstone -l 160: 30 sec 5021 calls 167.36 calls/sec 20.57 msec/call
nhfsstone -l 170: 29 sec 5019 calls 173.06 calls/sec 22.51 msec/call
nhfsstone -l 180: 27 sec 5005 calls 185.37 calls/sec 24.42 msec/call
nhfsstone -l 190: 26 sec 5001 calls 192.34 calls/sec 29.98 msec/call
nhfsstone -l 200: 26 sec 5001 calls 192.34 calls/sec 32.91 msec/call
nhfsstone -l 210: 26 sec 5008 calls 192.61 calls/sec 34.59 msec/call

						Masataka Ohta