Print

Add to Reputation:  

What do you think of this post?

I agree I disagree  
Comment:

[Kratos]

http://mitchribar.com/2013/02/how-to-stop-youtube-sucking-windows-guide/

Lazy clicking the link? Follow below

1.Click the Start button, type “cmd”, and right click the icon to ‘Run As Administrator’

2.You will likely see a UAC prompt, hit “Yes”

3.The command prompt window will open, this is where you will type in the commands to set your firewall rules

4.Enter the following command and hit Enter. If it works, you should see a big “OK”. (If you do not see the word OK, enable your firewall service)

netsh advfirewall firewall add rule name="MITCHRIBARYTUBE" dir=in action=block remoteip=173.194.55.0/24,206.111.0.0/16 enable=yes

You can remove that rule above by typing this command

netsh advfirewall firewall delete rule name="MITCHRIBARYTUBE"

I added the ip ranges in my router and I went to visit this video because I can't stop staring at Mila Kunis.



Right click the video and select show video info. You should see your kbps increase after blocking the ips. I play all of my youtube videos at 1080p and it fully loads on a 60Mb/s connection. Before it would just buffer on 360p.

"Why do these commands create a better streaming experience? Your ISP is throttling downloads from servers (CDN) that host cached videos. By rejecting these IP address ranges you will force the video to be served to you directly. This harnesses the full download speed of your internet connection. Other people can dive into the complexity much better than I ever could, but that’s the overall theme"

[killermonkey]

Why would they throttle speeds from cache locations but not the original, that makes absolutely no sense.

I thought Google throttled the buffer rate to reduce bandwidth usage on their end of videos that were played but abandoned. (ie why send you the whole video if you only watch the first half)

[Kratos]

Why would they throttle speeds from cache locations but not the original, that makes absolutely no sense.

I thought Google throttled the buffer rate to reduce bandwidth usage on their end of videos that were played but abandoned. (ie why send you the whole video if you only watch the first half)

More info:

"I've been doing some more research today. I did some traffic analyzing using Fiddler (an HTTP request logging tool), and one difference between using my Verizon hot spot and using my Time Warner Cable connection is that the video seems to be delivered in a different way.

The request for the video using my cable internet resulted in the video being delivered with this request: http://o-o---preferred---sn-mv-p5qe---v17---lscache1.c.youtube.com/videoplayback?algorithm=throttle-factor&burst=40&cp=U0hUSFVQUl9JTUNONF9NSlZCOkxfb2xNUng0TVda&cpn=5FLV3X0xXV3ARFBJ&expire=1353554143&factor=1.25&fexp=906373%2C910100%2C916612%2C922401%2C920704%2C912806%2C927201%2C925706%2C922403%2C913546%2C913556%2C916805%2C920201%2C901451&gcr=us&id=85b2e0b337d74c06&ip=69.76.216.21&ipbits=8&itag=34&keepalive=yes&key=yt1&ms=au&mt=1353529212&mv=m&range=1781760-3563519&signature=D59CEFD67C81BD6A7CD8CA541828E17694E3139B.BC4FDA68789EEA0D4F329DB248A189AA0DA1C7F0&source=youtube&sparams=algorithm%2Cburst%2Ccp%2Cfactor%2Cgcr%2Cid%2Cip%2Cipbits%2Citag%2Csource%2Cupn%2Cexpire&sver=3&upn=-SlA8AnXQxc

For the techies out there, it looks like this problem could actually be caused by intentional bandwidth throttling that is actually permitted by YouTube and built into their system.

Further researching led me to this:

https://peering.google.com/about/peering_policy.html
"