On Thu, Jul 28, 2011 at 12:43, Reinier Battenberg <[email protected]> wrote: > Hi, > Does that mean my ISP is not using the google cache at UTL, or was I just not > lucky today? Or was my test just flawed? If so, how can i test if i get my > youtube videos from the UTL gcache? And what servernames do other people (in > uganda) see when they load a utube video? >
According to Google (http://mybroadband.co.za/vb/showthread.php/241596-Google-Global-Cache-%28GGC%29), the video will be served from the 'best' location. In your case, that video may not have been in the google node at UTL but if it is played by many people here, it will be considered popular and the Google servers will then push it to the UTL cache. In other words, the UTL cache will usually server the popular videos. A good example is trying the popular videos here like songs by Chameleone, Iryn Namubiru etc. Regards, Wilson > I clicked a random movie for my test, i happened to be this one > http://www.youtube.com/watch?v=g7xQBNngzC8&feature=relmfu > > btw, that cache seems to be doing its job, UTL is pushing 30Mb/s through the > UIXP, quite impressive, that is about 6 times more than before they started > sharing the cache. You can see the stats of the Ugandan internet here > http://stats.uixp.co.ug/ > > Here is the traceroute. > > reinier@mountlab6:~$ traceroute o-o.preferred.bharti- > bom1.v5.lscache3.c.youtube.com > traceroute to o-o.preferred.bharti-bom1.v5.lscache3.c.youtube.com > (182.79.254.156), 30 hops max, 60 byte packets > 1 ipcop.mountbatten.net (192.168.38.1) 3.080 ms * * > 2 41.220.13.21 (41.220.13.21) 5.680 ms 5.881 ms 6.126 ms > 3 41.220.12.129 (41.220.12.129) 21.764 ms 21.999 ms 22.218 ms > 4 192.168.12.1 (192.168.12.1) 41.478 ms 41.684 ms 41.897 ms > 5 192.168.145.1 (192.168.145.1) 42.247 ms 46.825 ms 47.091 ms > 6 41.220.12.41 (41.220.12.41) 48.178 ms 45.303 ms 45.459 ms > 7 41.220.12.49 (41.220.12.49) 45.691 ms 51.389 ms 37.222 ms > 8 if-ctu-edge-ci.data.co.ug (41.220.12.33) 48.018 ms 48.192 ms 52.393 ms > 9 41.84.196.145 (41.84.196.145) 35.289 ms 41.84.196.137 (41.84.196.137) > 35.528 ms 35.290 ms > 10 41.84.192.129 (41.84.192.129) 77.292 ms 77.479 ms 76.523 ms > 11 dsl-del-static-045.45.246.61.airtelbroadband.in (61.246.45.45) 218.890 ms > 219.089 ms 219.580 ms > 12 AES-Static-133.36.144.59.airtel.in (59.144.36.133) 235.195 ms 234.854 ms > 211.352 ms > 13 AES-Static-190.36.144.59.airtel.in (59.144.36.190) 356.806 ms 357.538 ms > 362.792 ms > 14 203.101.100.21 (203.101.100.21) 362.777 ms 398.357 ms 368.134 ms > 15 203.101.100.26 (203.101.100.26) 367.486 ms 367.569 ms 388.039 ms > 16 * * * > 17 * * * > 18 * * * > 19 * * * > 20 * * * > 21 * * * > 22 * * * > 23 * * * > 24 * * * > 25 * * * > 26 * * * > 27 * * * > 28 * * * > 29 * * * > 30 * * * > > > > -- > rgds, > > Reinier Battenberg > Director > Mountbatten Ltd. > +256 758 801 749 > www.mountbatten.net > http://twitter.com/batje > http://twitter.com/mapuganda > > > _______________________________________________ > The Uganda Linux User Group: http://linux.or.ug > > Send messages to this mailing list by addressing e-mails to: [email protected] > Mailing list archives: http://www.mail-archive.com/[email protected]/ > Mailing list settings: http://kym.net/mailman/listinfo/lug > To unsubscribe: http://kym.net/mailman/options/lug > > The Uganda LUG mailing list is generously hosted by INFOCOM: > http://www.infocom.co.ug/ > > The above comments and data are owned by whoever posted them (including > attachments if any). The mailing list host is not responsible for them in any > way. > _______________________________________________ The Uganda Linux User Group: http://linux.or.ug Send messages to this mailing list by addressing e-mails to: [email protected] Mailing list archives: http://www.mail-archive.com/[email protected]/ Mailing list settings: http://kym.net/mailman/listinfo/lug To unsubscribe: http://kym.net/mailman/options/lug The Uganda LUG mailing list is generously hosted by INFOCOM: http://www.infocom.co.ug/ The above comments and data are owned by whoever posted them (including attachments if any). The mailing list host is not responsible for them in any way.
