YouTube Video uploading

[#1]

Quote from: MikesMovies

Quote from: Kelly Not sure.    I think we worked out it was an MTU issue. OP: Have you been playing with your MTU? MTU?

What is an MTU and why does it matter?
Your MTU, or Maximum Transmission Unit, is the configured packet size your computer uses when sending packets of data to other computers. In the context of ADSL, an MTU is commonly set between 1400 and 1500 bytes.
There are some critical sizes for the MTU, and performance problems can arise if your MTU is set too high. Contrary to what might seem sensible, lowering your MTU can actually raise your data transfer speeds (to a point).
Some problems you may see if your MTU is too large:
    Very low upload/download speeds
    On an otherwise 'clean' data path (no packet loss, low latency).
    FTP or file uploads/downloads which stall
    Downloads stop after the first 1-2 kilobytes downloaded (including downloading a server file listing in an FTP client, which is actually just another file download and subject to the same issues).
    Some web or FTP sites work fine for downloads, but others operate slowly or not at all
    (the difference being whether the remote site is interacting with the network in a manner which makes this issue show up). In particular, some sites may encounter a problem related to Path MTU Discovery, made worse by a large MTU.

Find the MTU setting in your modem/router, and try changing the value to either 1458 or 1430.
Restart your modem/router, and then restart your PC, and see whether a lower MTU helps.
While I don't upload to YouTube, my connection performs measurably faster and has less connection issues, when my gateway MTU is changed from the default of typically 1500 or 1492, to either 1458 or 1430 (depending on which gateway I am playing with this week !).

[#2]

Hmm I have this, loads more but I can't seem to attach a zip file to this board.
No.    Time          Source                Destination          Protocol Length Info
      1 0.000000000    74.125.195.117        192.168.1.71          TCP      66    http > bmc-patroldb [ACK] Seq=1 Ack=1 Win=1981 Len=0 SLE=1431 SRE=7151
Frame 1: 66 bytes on wire (528 bits), 66 bytes captured (528 bits) on interface 1
Ethernet II, Src: Technico_39:19:36 (a4:b1:e9:39:19:36), Dst: Foxconn_b0:61:38 (00:01:6c:b0:61:38)
Internet Protocol Version 4, Src: 74.125.195.117 (74.125.195.117), Dst: 192.168.1.71 (192.168.1.71)
Transmission Control Protocol, Src Port: http (80), Dst Port: bmc-patroldb (1313), Seq: 1, Ack: 1, Len: 0
No.    Time          Source                Destination          Protocol Length Info
      2 0.010572000    74.125.195.117        192.168.1.71          TCP      66    [TCP Dup ACK 1#1] http > bmc-patroldb [ACK] Seq=1 Ack=1 Win=1981 Len=0 SLE=1431 SRE=8581
Frame 2: 66 bytes on wire (528 bits), 66 bytes captured (528 bits) on interface 1
Ethernet II, Src: Technico_39:19:36 (a4:b1:e9:39:19:36), Dst: Foxconn_b0:61:38 (00:01:6c:b0:61:38)
Internet Protocol Version 4, Src: 74.125.195.117 (74.125.195.117), Dst: 192.168.1.71 (192.168.1.71)
Transmission Control Protocol, Src Port: http (80), Dst Port: bmc-patroldb (1313), Seq: 1, Ack: 1, Len: 0
No.    Time          Source                Destination          Protocol Length Info
      3 0.010624000    192.168.1.71          74.125.195.117        HTTP    1484  Continuation or non-HTTP traffic
Frame 3: 1484 bytes on wire (11872 bits), 1484 bytes captured (11872 bits) on interface 1
Ethernet II, Src: Foxconn_b0:61:38 (00:01:6c:b0:61:38), Dst: Technico_39:19:36 (a4:b1:e9:39:19:36)
Internet Protocol Version 4, Src: 192.168.1.71 (192.168.1.71), Dst: 74.125.195.117 (74.125.195.117)
Transmission Control Protocol, Src Port: bmc-patroldb (1313), Dst Port: http (80), Seq: 11441, Ack: 1, Len: 1430
Hypertext Transfer Protocol
No.    Time          Source                Destination          Protocol Length Info
      4 0.021647000    74.125.195.117        192.168.1.71          TCP      66    [TCP Dup ACK 1#2] http > bmc-patroldb [ACK] Seq=1 Ack=1 Win=1981 Len=0 SLE=1431 SRE=10011
Frame 4: 66 bytes on wire (528 bits), 66 bytes captured (528 bits) on interface 1
Ethernet II, Src: Technico_39:19:36 (a4:b1:e9:39:19:36), Dst: Foxconn_b0:61:38 (00:01:6c:b0:61:38)
Internet Protocol Version 4, Src: 74.125.195.117 (74.125.195.117), Dst: 192.168.1.71 (192.168.1.71)
Transmission Control Protocol, Src Port: http (80), Dst Port: bmc-patroldb (1313), Seq: 1, Ack: 1, Len: 0
No.    Time          Source                Destination          Protocol Length Info
      5 0.021693000    192.168.1.71          74.125.195.117        HTTP    1484  [TCP Fast Retransmission] Continuation or non-HTTP traffic
Frame 5: 1484 bytes on wire (11872 bits), 1484 bytes captured (11872 bits) on interface 1
Ethernet II, Src: Foxconn_b0:61:38 (00:01:6c:b0:61:38), Dst: Technico_39:19:36 (a4:b1:e9:39:19:36)
Internet Protocol Version 4, Src: 192.168.1.71 (192.168.1.71), Dst: 74.125.195.117 (74.125.195.117)
Transmission Control Protocol, Src Port: bmc-patroldb (1313), Dst Port: http (80), Seq: 1, Ack: 1, Len: 1430
Hypertext Transfer Protocol
No.    Time          Source                Destination          Protocol Length Info
      6 0.032020000    74.125.195.117        192.168.1.71          TCP      66    [TCP Dup ACK 1#3] http > bmc-patroldb [ACK] Seq=1 Ack=1 Win=1981 Len=0 SLE=1431 SRE=11441
Frame 6: 66 bytes on wire (528 bits), 66 bytes captured (528 bits) on interface 1
Ethernet II, Src: Technico_39:19:36 (a4:b1:e9:39:19:36), Dst: Foxconn_b0:61:38 (00:01:6c:b0:61:38)
Internet Protocol Version 4, Src: 74.125.195.117 (74.125.195.117), Dst: 192.168.1.71 (192.168.1.71)
Transmission Control Protocol, Src Port: http (80), Dst Port: bmc-patroldb (1313), Seq: 1, Ack: 1, Len: 0
No.    Time          Source                Destination          Protocol Length Info
      7 0.032074000    192.168.1.71          74.125.195.117        HTTP    1484  Continuation or non-HTTP traffic
Frame 7: 1484 bytes on wire (11872 bits), 1484 bytes captured (11872 bits) on interface 1
Ethernet II, Src: Foxconn_b0:61:38 (00:01:6c:b0:61:38), Dst: Technico_39:19:36 (a4:b1:e9:39:19:36)
Internet Protocol Version 4, Src: 192.168.1.71 (192.168.1.71), Dst: 74.125.195.117 (74.125.195.117)
Transmission Control Protocol, Src Port: bmc-patroldb (1313), Dst Port: http (80), Seq: 12871, Ack: 1, Len: 1430
Hypertext Transfer Protocol
No.    Time          Source                Destination          Protocol Length Info
      8 0.043311000    74.125.195.117        192.168.1.71          TCP      66    [TCP Dup ACK 1#4] http > bmc-patroldb [ACK] Seq=1 Ack=1 Win=1981 Len=0 SLE=1431 SRE=12871
Frame 8: 66 bytes on wire (528 bits), 66 bytes captured (528 bits) on interface 1
Ethernet II, Src: Technico_39:19:36 (a4:b1:e9:39:19:36), Dst: Foxconn_b0:61:38 (00:01:6c:b0:61:38)
Internet Protocol Version 4, Src: 74.125.195.117 (74.125.195.117), Dst: 192.168.1.71 (192.168.1.71)
Transmission Control Protocol, Src Port: http (80), Dst Port: bmc-patroldb (1313), Seq: 1, Ack: 1, Len: 0
No.    Time          Source                Destination          Protocol Length Info
      9 0.043333000    192.168.1.71          74.125.195.117        HTTP    1484  Continuation or non-HTTP traffic
Frame 9: 1484 bytes on wire (11872 bits), 1484 bytes captured (11872 bits) on interface 1
Ethernet II, Src: Foxconn_b0:61:38 (00:01:6c:b0:61:38), Dst: Technico_39:19:36 (a4:b1:e9:39:19:36)
Internet Protocol Version 4, Src: 192.168.1.71 (192.168.1.71), Dst: 74.125.195.117 (74.125.195.117)
Transmission Control Protocol, Src Port: bmc-patroldb (1313), Dst Port: http (80), Seq: 14301, Ack: 1, Len: 1430
Hypertext Transfer Protocol

[#3]

The best thing to do would be raise a support ticket at http://contactus.plus.net that then offers an option to attach a file.

[#4]

Took these screen shots in case they help?

[#5]

OK can you walk me through what you want me to do with the capture software and what you want me to export, thanks?

[#6]

PlusNet support, Question #74234136  refers thanks
18:03 still slowly uploading to you at the mo, 83% done for a 4mb zip file! hmm slow to you as well

[#7]

Quote from: Kelly

Quote from: ejs I don't think much progress was ever made on the previous recent instance of slow uploads to youtube. Not sure.    I think we worked out it was an MTU issue. OP: Have you been playing with your MTU?

Looked up MTU to see what it is, mine seems to be set at MTU 32768, from google it seems win xp should be 1500, not sure as I don't understand this?

[#8]

yeah default mtu is 1500 sounds like some software or driver update you did caused the fault
just google set mtu to 1500
you run a command prompt and type in a command line which fixes the pc's setting
also your better off using 1492 for most uk isp's

[#9]

I doubt your mtu is actually 32768, if you haven't changed your mtu, leave it alone at 1500. Because 1500 is the default mtu, pretty much everything should be fine with it.

Quote from: Kelly

Quote from: ejs I don't think much progress was ever made on the previous recent instance of slow uploads to youtube. Not sure.    I think we worked out it was an MTU issue.

Well if there was a conclusion to Razer's thread, it's not on the forums. And if a MTU of 1500 is a problem, that implies pretty much everyone should change their mtu.

[#10]

Quote from: nanotm

yeah default mtu is 1500 sounds like some software or driver update you did caused the fault just google set mtu to 1500 you run a command prompt and type in a command line which fixes the pc's setting also your better off using 1492 for most uk isp's

Hi and thanks, OK I have set it to 1492 and am conducting a test upload to youtube, at the moment a 149mb file, its saying 5% done and 37 mins to go! we shall see!

[#11]

1500 is the default because its the theoretical maximum but in reality a phone circuit can be tuned to except any value (its how certain companies maintain completely secure internal  network comm's despite sending everything over phone lines) if your mtu value is set to high or too low then it will cause cause problems however if you "fine tune" to the optimal value of your phone exchange (mine is 1492 as are most although some do have different values) then you get less ping time, fewer packets "lost" etc etc because your running a "matched sync" instead of a mismatched sync ....

its very minor though years ago bt set some exchanges at 1250 doing a trial and whilst downloads worked fine uploads didn't work at all ....

@MM
allowing for the fact its peak time and YT will be overused (so less speed on the upload circuit) that's already sounding faster than before  but be aware windows is terrible at guesstimating time

[#12]

For Windows XP you could do a tweak test at http://www.dslreports.com/tweaks and see what that recommends. It's possible data transfer speed might benefit from RWIN being increased.
Best not try this alongside the upload though.

[#13]

Hi, well its now jumped to 179 mins and is still on 5% I started it at 18:37 and its now 18:54.
Screen shot attached, interestingly far less connections just now???
Bailed out, predicted time had now bearing on reality

[#14]

Hi
I got these results:
http://www.dslreports.com/tweakr/block:3b16d10?service=dsl&speed=16384&os=winXP&via=normal

[#15]

The download test result is very good. RWIN is 256960 which is fine and settings shown for the other parameters seem OK to me.
However the MTU sending and receiving MTUs look peculiar, 32160 and 1500 bytes respectively. is 32K the value set on the router? The test shows that oddity doesn't appear to affect download, but not sure if it will upset uploads.