[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] Windows 2008 - slow upload
-------- Original Message -------- Subject: Re: [Xen-users] Windows 2008 - slow upload From: James Harper <james.harper@xxxxxxxxxxxxxxxx> To: Tomek <timor@xxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx Date: 03.08.2009 11:38 -------- Original Message -------- Subject: Re: [Xen-users] Windows 2008 - slow upload From: James Harper <james.harper@xxxxxxxxxxxxxxxx> To: Tomek <timor@xxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx Date: 03.08.2009 11:03Can you please try with vcpus=1 and see if that makes anydifference.It's not a solution but it would help me try and find one...I've changed vcpus to 1, and commented out cpus with no impact on networking. For now I have "Checksum Offload" and "Check checksum onRXpackets" both disabled.I think I'll need packet traces to get much further. Can you reproduce using iperf? (it is available for both windows and linux). If you can, then I can send you the details of the wireshark and tcpdump filters I'll need a capture from. Yes, I can reproduce it with iperf - downloading (works like a charm): iperf -c 192.168.x.1 -P 1 -i 1 -p 5001 -f K -t 10 -T 1 -S 0x04 ------------------------------------------------------------ Client connecting to 192.168.x.1, TCP port 5001 TCP window size: 16.0 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.x.2 port 47419 connected with 192.168.x.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0- 1.0 sec 108240 KBytes 108240 KBytes/sec [ 3] 1.0- 2.0 sec 106032 KBytes 106032 KBytes/sec [ 3] 2.0- 3.0 sec 107056 KBytes 107056 KBytes/sec [ 3] 3.0- 4.0 sec 108064 KBytes 108064 KBytes/sec [ 3] 4.0- 5.0 sec 105320 KBytes 105320 KBytes/sec [ 3] 5.0- 6.0 sec 107120 KBytes 107120 KBytes/sec [ 3] 6.0- 7.0 sec 107192 KBytes 107192 KBytes/sec [ 3] 7.0- 8.0 sec 106368 KBytes 106368 KBytes/sec [ 3] 8.0- 9.0 sec 107352 KBytes 107352 KBytes/sec [ 3] 9.0-10.0 sec 106552 KBytes 106552 KBytes/sec [ 3] 0.0-10.0 sec 1069328 KBytes 106932 KBytes/sec And uploading (wtf?): iperf.exe -c 192.168.x.2 -P 1 -i 1 -p 5001 -f k -t 10 ------------------------------------------------------------ Client connecting to 192.168.x.2, TCP port 5001 TCP window size: 8.00 KByte (default) ------------------------------------------------------------ [108] local 192.168.x.1 port 49314 connected with 192.168.x.2 port 5001 [ ID] Interval Transfer Bandwidth [108] 0.0- 1.0 sec 80.0 KBytes 655 Kbits/sec [108] 1.0- 2.0 sec 24.0 KBytes 197 Kbits/sec [108] 2.0- 3.0 sec 24.0 KBytes 197 Kbits/sec [108] 3.0- 4.0 sec 32.0 KBytes 262 Kbits/sec [108] 4.0- 5.0 sec 24.0 KBytes 197 Kbits/sec [108] 5.0- 6.0 sec 24.0 KBytes 197 Kbits/sec [108] 6.0- 7.0 sec 24.0 KBytes 197 Kbits/sec [108] 7.0- 8.0 sec 32.0 KBytes 262 Kbits/sec [108] 8.0- 9.0 sec 24.0 KBytes 197 Kbits/sec [108] 9.0-10.0 sec 24.0 KBytes 197 Kbits/sec [108] 0.0-10.4 sec 320 KBytes 251 Kbits/secWhen I'm sniffing on Dom0 when uploading from Win2k8-DomU then packets are "flying" slower when downloading and all runs fluently without any longer brakes. Could you send me details for filters in wireshark/tcpdump?I've tested same VLAN configuration from a linux-DomU and it runs normally - so it's not broken VLAN configuration. For now I'm downloading different versions of GPLPV drivers - maybe there is a regress in newest version... -- Regards, Thomas. _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |