![]() to maximize the bandwidth going to/from you (regardless of revenue). Usually we’d try to launch things in the other direction, ie. Your account might be a part of some private experiment that changes something for you on some browser… just by virtue of your account id hash mod 1000 equalling some random const number, you might be a part of the browser experiment. ![]() Hi, disclaimer, I work at Google, but on parts of the Ads system and not YouTube and not the part of Ads that deals with YouTube (nor am I in management or privy to product launch decision making, quite removed from that part of the org actually).įrom random lunch conversations, back when we had them, the throttling behavior you’re describing is certainly technically and from an infrastructure perspective possible, but I’m doubtful it’s desired. If this pans out to be true for others, not cool. I could use some help verifying some of the above. This is also further evidence of throttling YouTube stream bit-rate based on the ISP connection/Google account as the DSL connection is less likely to experience traffic condition (in my area) that support masking YouTube stream bit-rate throttling.Īll of this is easily reproducible worth a look into. I have a second DSL connection and while staying logged into my Google account and only switching from my tethered cell connection to a DSL connection the YouTube bit-rate throttling will cease. But it’s not, because logging out of my Google account stops the bit-rate throttling exposing the local ISP (and YouTube) as capable of streaming at a much higher rate. Throttling during these times is not likely to be noticed and could be even justified as some kind of efficiency. ![]() So obviously, based on my account, Google knows who my ISP is, when the high traffic times are and how much and when to throttle video to match the ISP’s traffic pattern. The upshot here is Google appears to be throttling the streaming bit-rate for a YouTube video to match the traffic experienced at the ‘last mile’ ISP connection point based on history and not actual conditions as logging out of my Google account stops the YouTube bit-rate throttling and videos stream at the actual ISP’s maximum bit-rate. The ’ graph of past video view traffic’ is of note because it so closely parallels (pretty much exactly) the times I experience streaming bit-rate throttling when logged into my Google account. Google will display a “Experiencing Interruptions?” pop-up link on videos that are excessively buffering a stream and clicking on that pop-up link will open a web page displaying connection information, like your current ISP, a graph of past video view traffic for that ISP and more. This gives me some variety and options to access the internet. But, I also have a very slow (Geo-location reasons) but available DSL connection to compare with when needed. I live way out in a rural area and am pretty much dependent upon cell phone base access to the internet. I have a pretty unique situation as far as digital access goes. The reasons are not entirely clear but what is clear is one of Googles apparent goals. Google is throttling my YouTube streaming based on my account (see above). I have been putting all of this together at least on the account throttling side. It gets even weirder! Checkout this excerpt from a followup comment I left.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |