Re: Getting OpenVZ container to run at 1000MB (Network speed) instead of 100MB [message #36429 is a reply to message #36422] |
Thu, 18 June 2009 09:06 |
khorenko
Messages: 533 Registered: January 2006 Location: Moscow, Russia
|
Senior Member |
|
|
i checked on my local nodes and got almost the same results of network speeds on a Hardware Node and inside a Container:
Server:
[server iperf-2.0.4]# src/iperf -s -w 256K
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 256 KByte (WARNING: requested 256 KByte)
------------------------------------------------------------
[ ID] Interval Transfer Bandwidth
[ 5] local <serverIP> port 5001 connected with <clientHN> port 48227
[ 5] 0.0-10.0 sec 1.10 GBytes 941 Mbits/sec
[ ID] Interval Transfer Bandwidth
[ 4] local <serverIP> port 5001 connected with <clientCT> port 57894
[ 4] 0.0-10.0 sec 1.10 GBytes 941 Mbits/sec
Client:
[clientHN iperf-2.0.4]# src/iperf -c <serverIP> -w 256K
------------------------------------------------------------
Client connecting to <serverIP>, TCP port 5001
TCP window size: 256 KByte (WARNING: requested 256 KByte)
------------------------------------------------------------
[ 3] local <clientHN> port 48225 connected with <serverIP> port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 1.10 GBytes 941 Mbits/sec
[clientHN iperf-2.0.4]# vzctl enter 101
entered into Container 101
-bash-3.2# su -
[root@localhost ~]# cd /tmp/iperf/iperf-2.0.4
[root@localhost iperf-2.0.4]# src/iperf -c <serverIP> -w 256K
------------------------------------------------------------
Client connecting to <serverIP>, TCP port 5001
TCP window size: 256 KByte (WARNING: requested 256 KByte)
------------------------------------------------------------
[ 3] local <clientCT> port 57894 connected with <serverIP> port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 1.10 GBytes 941 Mbits/sec
Could you share your results in the same way?
Please, use nodes which are connected to the same switch to make a clear experiment.
Next thing to check is routing. May be packets from the CT do not go directly to the destination server but first go to some default router or so, which has 100Mb network card or connected to 100Mb switch or similar.
Hope this helps.
--
Konstantin
If your problem is solved - please, report it!
It's even more important than reporting the problem itself...
|
|
|