Is it just me or leads running "netio -s" directly on the router to unreliable results?
G 2,4GHz 40MHz Channel 4, HT40+, running netio -s on WNDR3700 router and netio -t on Laptop (Win7 64bit, Intel Wifi Link 5300) distance of 20feets
I obtain
TCP connection established.
Packet size 1k bytes: 3396.70 KByte/s Tx, 8112.94 KByte/s Rx.
Packet size 2k bytes: 3298.02 KByte/s Tx, 8996.29 KByte/s Rx.
Packet size 4k bytes: 3310.89 KByte/s Tx, 8394.06 KByte/s Rx.
Packet size 8k bytes: 3350.48 KByte/s Tx, 9391.06 KByte/s Rx.
Packet size 16k bytes: 3426.79 KByte/s Tx, 8079.38 KByte/s Rx.
Packet size 32k bytes: 3188.34 KByte/s Tx, 9000.88 KByte/s Rx.
Done.
very close to the router (6 feets)
Packet size 1k bytes: 3973.91 KByte/s Tx, 10.06 MByte/s Rx.
Packet size 2k bytes: 4187.24 KByte/s Tx, 10.44 MByte/s Rx.
Packet size 4k bytes: 4173.92 KByte/s Tx, 10.82 MByte/s Rx.
Packet size 8k bytes: 4176.71 KByte/s Tx, 10.13 MByte/s Rx.
Packet size 16k bytes: 4332.23 KByte/s Tx, 10.38 MByte/s Rx.
Packet size 32k bytes: 4347.95 KByte/s Tx, 9940.31 KByte/s Rx.
Done.
however running the netio server on a Gbit wire connected computer and using the same client the results change:
TCP connection established.
Packet size 1k bytes: 4720.70 KByte/s Tx, 6622.10 KByte/s Rx.
Packet size 2k bytes: 5102.82 KByte/s Tx, 7138.99 KByte/s Rx.
Packet size 4k bytes: 5286.17 KByte/s Tx, 6797.29 KByte/s Rx.
Packet size 8k bytes: 5035.18 KByte/s Tx, 7907.19 KByte/s Rx.
Packet size 16k bytes: 5026.45 KByte/s Tx, 7147.51 KByte/s Rx.
Packet size 32k bytes: 5523.43 KByte/s Tx, 7240.45 KByte/s Rx.
Done.
The gap between the TX and Rx rate is a lot closer, but overall Rx is much lower too.
very close to the router (6 feets)
TCP connection established.
Packet size 1k bytes: 10.71 MByte/s Tx, 9.54 MByte/s Rx.
Packet size 2k bytes: 13.53 MByte/s Tx, 9769.77 KByte/s Rx.
Packet size 4k bytes: 13.37 MByte/s Tx, 6171.75 KByte/s Rx.
Packet size 8k bytes: 13.73 MByte/s Tx, 10.53 MByte/s Rx.
Packet size 16k bytes: 10.53 MByte/s Tx, 8468.86 KByte/s Rx.
Packet size 32k bytes: 12.77 MByte/s Tx, 9186.46 KByte/s Rx.
Done.
Now the Tx rate is a lot higher, kinda strange why does the distance affect the Tx rate so extremly but the Rx rate only moderately?
now the netio server running on the Laptop client (with the Intel wifi link 5300 card), and the client is the Gbit computer
TCP connection established.
Packet size 1k bytes: 4229.33 KByte/s Tx, 3457.96 KByte/s Rx.
Packet size 2k bytes: 10155.11 KByte/s Tx, 3672.56 KByte/s Rx.
Packet size 4k bytes: 10.31 MByte/s Tx, 4010.57 KByte/s Rx.
Packet size 8k bytes: 9468.00 KByte/s Tx, 4066.27 KByte/s Rx.
Packet size 16k bytes: 10.11 MByte/s Tx, 3835.62 KByte/s Rx.
Packet size 32k bytes: 10.59 MByte/s Tx, 3839.10 KByte/s Rx.
Done.
this is the output from the Gbit client, so the results must be reversed and again the Tx values are extremely low (Rx for the Gbit client, but Tx for the Wireless client running the netio server, I hope its not too confusing ).
So I did a "reality test" with a FTP file transfer (still 2,4 GHz network) (20 feets)
ftp server running on the Gbit client
download ->7.5 MB/s
upload/send -> 6.1 MB/s
ftp server running on the WNDR3700 router (pure-ftp)
download -> 6.6 MB/s
upload -> 3.1 MB/s
Does the hardware of the router restrict? (regarding the ftp transfer I would say it could be the filesystem, but netio delivers nearly the same results), and CPU load was never above 50%.
Has anybody an idea why the results for the Gbit client and the router differ so much? even If I run the netio server on the wireless client again I obtain the same bad Tx results, makes not much sense to me? (sry for the long post but I didn't want to leave out important information).
(Last edited by redcow on 25 Jan 2011, 01:10)