Resultados 1 a 2 de 2
  1. #1
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010

    [EN] Inside Apple’s Live Event Stream Failure: It Wasn’t A Capacity Issue

    Dan Rayburn | Tuesday September 9, 2014 | 06:26 PM

    Apple’s live stream of the unveiling of the iPhone 6 and Watch was a disaster today right from the start, with many users like myself having problems trying to watch the event. While at first I assumed it must be a capacity issue pertaining to Akamai, a deeper look at the code on Apple’s page and some other elements from the event shows that decisions made by Apple pertaining to their website, and problems with how they setup storage on Amazon’s S3 service, contributed the biggest problems to the event.

    Unlike the last live stream Apple did, this time around Apple decided to add some JSON (JavaScript Object Notation) code to the page which added an interactive element on the bottom showing tweets about the event. As a result, this was causing the page to make refresh calls every few milliseconds. By Apple making the decision to add the JSON code, it made the website un-cachable. By contrast, Apple usually has Akamai caching the page for their live events but this time around there would have been no way for Akamai to have done that, which causes a huge impact on the performance when it comes to loading the page and the stream. And since Apple embeds their video directly in the web page, any performance problems in the page also impacts the video. Akamai didn’t return my call asking for more details, but looking at the code shows there was no way Akamai could have cached it. This is also one of the reasons why when I tried to load the Apple live event page on my iPad, it would make Safari quit. That’s a problem with the code on the page, not with the video.

    Because of all the refresh calls from the JSON code, it looks like it artificially forced the player to degrade the quality of the video, dropping it down to a lower bitrate, because it thought there were more requests for the stream than there was. As for the foreign language translation that we heard for the first 27 minutes of the event, that’s all on Apple as they do the encoding themselves for their events, from the location the event is at. Clearly someone on Apple’s side didn’t have the encoder setup right and their primary and backup streams were also way out of sync. So whatever Apple sent to Akamai’s CDN is what got delivered and in this case, the video was overlaid with a foreign language track. I also saw at least one instance where I believe that Apple’s encoder(s) were rebooted after the event had already started which probably also contributed to the “could not load movie” and “you don’t have permission to access” error messages.

    Looking at the metadata from the event page, you could see that Apple was hosting content from the interactive element on the event page on Amazon’s S3 cloud storage service. From what I can tell, it looks like Apple setup the content in a single bucket on S3 with little to no cache hit ratio, with poor bucket configuration. Amazon didn’t reply to my request for more info, but it’s clear that Apple didn’t setup their S3 storage correctly, which caused huge performance issues when all the requests hit Amazon’s network in a single location.

    As for Akamai’s involvement in the event, they were the only CDN Apple used. Traceroutes from all over the planet (thanks to all who sent them in to me) showed that Apple relied solely on Akamai for the delivery. Without Akamai being able to cache Apple’s webpage, the performance to the videos took a huge hit. If Akamai can’t cache the website at the edge, then all requests have to go back to a central location, which defeats the whole purpose of using Akamai or any other CDNs to begin with. All CDNs architecture is based on being able to cache content, which in this case, Akamai clearly was not able to do. The below chart from third-party web performance provider Cedexis shows Akamai’s availability dropping to 98.5% in Eastern Europe during the event, which isn’t surprising if no caching is being used.

    The bottom line with this event is that the encoding, translation, JavaScript code, the video player, the call to S3 single storage location and the millisecond refreshes all didn’t work properly together and was the root cause of Apple’s failed attempt to make the live stream work without any problems. So while it would be easy to say it was a CDN capacity issue, which was my initial thought considering how many events are taking place today and this week, it does not appear that a lack of capacity played any part in the event not working properly. Apple simply didn’t provision and plan for the event properly.

  2. #2
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Jerrod • 12 minutes ago

    This is classic click-bait and we all fell for it. There is nothing here but baseless speculation and a fundamental lack of understanding of how "caching" works on the web. Please stop sharing this article.

    freediverx • 30 minutes ago

    How does this explain the same issues occurring on Apple TV, where presumably there was no JSON code to provide Twitter feed updates?

    SamRobinson • 7 hours ago

    Did the author of this article see the massive web attacks via IPViking on San Francisco during the webcast?

    Many came from Brazil and South Korea at the beginning of the live webcast. They even knocked the homepage offline.

    Brazil attacks were only 500-600 in one minute, in the two hours I monitored, and all focused on San Francisco. Brazil never launched another attack until a few hours until after the live stream.

    It looked like losing missile command on the Atari 2600.

    The dual language was Apple's fault. The outages were web attacks.

    If I had a tinfoil hat....

    Ryszard2 • 9 hours ago

    The web stream, after about half an hour, started to work flawlessly. Unless you claim that Apple completely rewrote the web page code in that time, I don't see how your theory could possibly be correct. And as others here have noted, the AppleTV feed also had issues, although the faulty page coding you blame was not part of it.

    Something went wrong, but it was something more than what you claim.

    CraigM • 14 hours ago

    The encoding and audio track mixing was broken from T-15 or more when the auditorium feed went live. An obvious auditorium audio feed was overlaid by a second audio of pop tracks.

    Interestingly, when it immediately glitched at the top of the hour and lost sync when it recovered we picked up the translation track and a number of efforts seem to have been made to drop the volume as they seemed unable to drop the spurious track.

    The trouble was that each stream restart brought the audio levels back up, so mist of the fixes were rolled back each time.

    In short, quite the least professional stream I've seen from Apple in many years of watching ... can't believe heads won't roll ...
    Última edição por 5ms; 10-09-2014 às 11:47.

Permissões de Postagem

  • Você não pode iniciar novos tópicos
  • Você não pode enviar respostas
  • Você não pode enviar anexos
  • Você não pode editar suas mensagens