![About CBC ,[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (19)
Destaque
Destaque (20)
Semelhante a Cache Optimization with Akamai
Semelhante a Cache Optimization with Akamai (20)
Mais de Blake Crosby
Mais de Blake Crosby (8)
Último
Último (20)
Cache Optimization with Akamai
- 1. Blake Crosby Julian Dunn Media Operations and Technology CBC/Radio-Canada Cache Optimization & Origin Infrastructure Reduction Using Akamai Site Delivery
- 11. Typical Origin Response Codes
- 16. How We Did It Content-Type: text/css Last-Modified: Mon, 07 Jun 2010 15:59:39 GMT Etag: "8a14b9cd-84a-c29470c0" Cache-Control: public, max-age=1557 Expires: Tue, 06 Jul 2010 21:38:51 GMT Date: Tue, 06 Jul 2010 21:12:54 GMT X-Cache: TCP_IMS_HIT from a72-246-43-6 (AkamaiGHost/5.9.4-6329478) (-) X-Cache-Key: /L/1849/9617/0s/www.cbc.ca/includes/objects/program-switcher/switcher.css X-True-Cache-Key: /L/www.cbc.ca/includes/objects/program-switcher/switcher.css X-Akamai-Session-Info: name=PARENT_SETTING; value=TD X-Serial: 1849 Connection: keep-alive Vary: Accept-Encoding X-Check-Cacheable: YES
- 19. Examples (Quebec Earthquake: June 23, 2010)
- 20. Examples (Quebec Earthquake: June 23, 2010)
- 21. Examples (Quebec Earthquake: June 23, 2010)
- 22. Examples (FIFA World Cup: June 11, 2010)
- 23. Examples (FIFA World Cup: June 11, 2010)
Notas do Editor
- Emphasize that we’re primarily a news site and this has certain implications for the longevity of our content – more later…
- Talk about why we optimize too. These are reasons for choosing Akamai DSD but we also optimize to hold the line on CapEx and OpEx growth.
- Somewhere in here we want to talk about h uch of the CDN’s value is only realized when it serves > 50% of your content.
- At the end of this we segue into the next slide by saying you place the needle on the spectrum by understanding your business context…
- Content is frequently updated when news breaks Old news is irrelevant news – access patterns bear this out
- The site – and the origin – must stay up no matter how much traffic hits. After that, the content must be fresh. To the business, stale content is worse than no content at all. Cost is mitigated through non-technical means, I.e. choosing a 95 th percentile billing model for DSD traffic so we don’t get hammered on cost by spikes.
- We’ve been gradually refining our approach, tools, techniques and architecture over the last ten years and we’ve learned a lot. Executing dynamic code for identical requests is silly (Newsdelivery) Don’t ignore architectural changes that you should make at the origin – CDN can only help so much. If your origin stinks, the edge will too. TTL means the time that Akamai will wait before checking the origin for freshness – doesn’t mean that the object will necessarily be retrieved, if it is already in-cache and fresh.
- Need to validate these numbers.
- Point out that 83.6% of the requests are 304 Not-Modified, which bears out our strategy of heavily using If-Modified-Since