JshWright wrote:
The default "us" Ubuntu mirror is in the UK. I would still expect better speeds than you're seeing, but you should probably try a different (closer) mirror. There's a whole lot of internet between your node and London (as your traceroute shows).
If you _are_ interested in a local caching proxy, I currently run one in Newark, and hope to add a few more in other DC's in the near future.
http://linsides.com/services/aptcache/I guess what I'm saying is that it seems counterintuitive that a high quality DC like HE would show such a glaring throughput differential compared to my office and house, both of which are here on the left edge of California with a whole lotta internet between here and wherever the default Ubuntu apt cache is. FWIW I hit both the 91.189.92.166 and 91.189.92.167 addresses when trying to get past the even-worse timeouts I was suffering the other night with this.
I know there are myriad workarounds, heck I was even prepared to proxy myself right through NJ, ATL or DAL where there were no issues with my apt-get maneuvers nor in my scp tests between this host and my Linodes in those DCs, but the bottom line is that the whole point of apt is to just make it happen... right? It's not like I'm expecting a default config to perform well in some far-off place, but rather expecting a default North American config to perform _reasonably_ well in a well-respected and performant North American datacenter.
And BTW this is not a gripe, rather a puzzling anomaly that I can reproduce in my Linodes deployed at HE from a couple years ago through ones deployed two days ago.
FAQ
Search
Members
Register
Login [ Anonymous ]
