Quote:
Originally Posted by bluebox
So do a "swapon -s" and check whether the server is using a noticeable amount of swap. Some kb are usual.
|
Filename Type Size Used Priority
/dev/hda3 partition 16386292 148 -1
I also ran iperf. Not sure if that is great tool for networkd performance, but here's the results from the server side with client connects:
Server and client IP's have been changed to protect the innocent.
server=111.11.111.11
client= 222.22.222.22
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
[ 4] local 111.11.111.11 port 5001 connected with 222.22.222.22 port 53814
[ ID] Interval Transfer Bandwidth
[ 4] 0.0-10.1 sec 111 MBytes 91.8 Mbits/sec
[ 5] local 111.11.111.11 port 5001 connected with 222.22.222.22 port 53815
[ 5] 0.0-10.1 sec 110 MBytes 90.9 Mbits/sec
------------------------------------------------------------
Client connecting to 222.22.222.22, TCP port 5001
TCP window size: 165 KByte (default)
------------------------------------------------------------
[ 5] local 111.11.111.11 port 34319 connected with 222.22.222.22 port 5001
[ 5] 0.0-10.0 sec 108 MBytes 90.4 Mbits/sec
[ 4] local 111.11.111.11 port 5001 connected with 222.22.222.22 port 53816
------------------------------------------------------------
Client connecting to 222.22.222.22, TCP port 5001
TCP window size: 40.3 KByte (default)
------------------------------------------------------------
[ 6] local 111.11.111.11 port 34320 connected with 222.22.222.22 port 5001
[ 6] 0.0-10.0 sec 96.6 MBytes 80.9 Mbits/sec
[ 4] 0.0-10.0 sec 92.6 MBytes 77.4 Mbits/sec