| Windows SFU | How to start NFS under Windows it's providing about 8MB/s aka 64mbps throughput (confirmed by sasa) |
| TrueGrid NFS Server | How to setup TrueGrid NFS Server |
| TrueGrid and NFSDream | How to setup TrueGrid and NFSDream |
| haneWIN | NFS Server for Windows HowTo |
| Winnfsd | Another NFS server |
| SOSSNT | Another NFS server |
| AlegroNFS source code | Commercial NFS server |
| Labtam ProNFS | Commercial NFS server |
| Cygwin NFSd | have lower performance |
HOW-TO: Setup Windows NFS/Services fot UNIX (SFU)
Also see this HowTo guide for information on setting up Microsoft's Services for Unix (which includes both an NFS server and client). Three things:
1. NFS or CIFS throughput test using 'cat' (PC→WDTV)
$ cd sharename_on_pc $ ls -l (to obtain filesize in bytes) $ time cat movie1.avi > /dev/null real 4m 13.10s user 0m 1.04s sys 0m 24.93s or $ time dd if=/sharename_on_pc/movie1.avi of=/dev/null bs=8k $ time dd if=/sharename_on_pc/movie1.avi of=/dev/null bs=16k
to calculate the speed of network transfer: (filesize in bytes)/(real time in seconds)*8/1000000 = and the result is in Mbps (megabits per second)
Make sure the file is on network share and not on local WDTV storage and is big enough (~100MB). You should test each file only once to make sure it is transferred over network and not copied from WDTV cache.
— droopysk 2009/03/12 09:15
2. throughput test using iperf
# ./iperf -c 192.168.2.151 ------------------------------------------------------------ Client connecting to 192.168.2.151, TCP port 5001 TCP window size: 16.0 KByte (default) ------------------------------------------------------------ [ 5] local 192.168.2.29 port 41278 connected with 192.168.2.151 port 5001 [ 5] 0.0-10.0 sec 28.1 MBytes 23.5 Mbits/sec
You need to install iperf on both the WDTV and another machine. For Linux or Windows, you can obtain iperf from here. For WDTV, you can install iperf via optware.
3. or you can try wget http transfer test but you need local webserver or very fast and near Internet webserver only very fast internet lines are useful because you may provide lower results and bottleneck is your ISP connection and not USB LAN adapter
wget -O /dev/null xxx.xxxx.com/big.jpg --2009-03-12 16:57:21-- http://xxx.xxxx.com.jpg Resolving xxx.xxxx.com... xx.xx.xx.xx Connecting to xxx.xxx.xx|xx.xx.xx.xx|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2418473 (2.3M) [image/jpeg] Saving to: `/dev/null' 100%[======================================>] 2,418,473 --.-K/s in 0.006s 2009-03-12 16:57:22 (382 MB/s) - `/dev/null' saved [2418473/2418473]
Testing configuration
Testing enviroment (TSST Corp 2GB USB2 FAT32 flash drive, LaCie 500MB USB2 HFS+ drive,
via Streaming
Notes:
— Netdata 2009/03/08 18:55
How to enable NFS under MacOSX
All tests using ext3-boot-0.3 distribution and a USB2 hard drive, using a 200-meg file. Test stats performed using “time dd … bs=16384” and calculating bits/sec. I used a 200meg file to minimize caching (the box has 128 meg of memory, of which 70meg is commonly cache buffers).
My new network dongle is a Trendnet TU2-ET100.
— Zorander 2009/02/18 08:51