Hi Ian, Patrick, We've had some fairly major problems with the Callplus Akamai cache in the past, especially with a customer of ours that makes heavy use of Apple developer resources -- these tend to have relatively little use, so the customer was often getting un-cached items, and performance of those downloads, frankly, sucked. If we got a cached item, it roared down. But if un-cached, they were experiencing sub-megabit download rates. Downloading beta OS distributions was so bad that they were downloading at home (via a different cache) and bringing them in on a flash stick. Akamai support was, uh, unhelpful. I'm being diplomatic. Now, I haven't had a complaint for a while. I don't know if that's just because the customer has learned to live with it knowing there's not a lot I can do, or if things have genuinely improved. -- don On 07/15/2010 12:21 PM, Ian Batterbee wrote:
Futher to my message below, uh, it seems there were some uh.. problems with the config after some BGP changes some time ago. I believe this has now been fixed, and we're now advertising approximately 2000 prefixes learned through APE towards Akamai's quagga box.
I guess this should put an end to the discussion about setting up an APE-connected Akamai cluster.
On 15 July 2010 10:23, Ian Batterbee
mailto:ibatterb(a)gmail.com> wrote: On 14 July 2010 15:31, Lincoln Reid
mailto:lincoln(a)acsdata.co.nz> wrote: Ideally someone from Callplus could chirp in here and clarify if they are feeding all the prefixes they learn at APE on to Akamai, or if there is a static list that will become out of date etc.
We set a community on anything we learn from APE, and send everything that has that community to Akamai. If someone can identify a particular route that isn't working as expected, let me know and I'll have a look.
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog