Frontend Caching - The "new" frontier

  • 2,005 views
Uploaded on

You have done all the caching tricks in the book on the server side: memcache, apc, database cache and so on and squeezed every millisecond out of it, now your site is as fast as it will ever get. …

You have done all the caching tricks in the book on the server side: memcache, apc, database cache and so on and squeezed every millisecond out of it, now your site is as fast as it will ever get. Well guess again !

Too often people forget that what you are effectively caching and creating with those technologies is the HTML part of the user response time, now if they are done correctly then HTML is 10 - 20% of your users response time, so there is room for a whole lot of improvements on those other 80 - 90%.

You will be taken through a couple of important steps to achieve this, such as how to optimize your JavaScript, CSS, Images, Cookies and a whole sleeve of other things that make frontend caching the magical place that it is.

After having attended this talk you will not only have learned to make your sites faster for your long term users but also people coming for the first time as well as people on slower connections.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,005
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
9

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • The user’s perception is more relevant than actual unload-to-onload response time. Definition of "user onload" is undefined or varies from one web page to the next.
  • User needs to download all components Coming for the first time Force refresh of the site Browser automagically cleared the cache based on settings
  • User needs to download all components Coming for the first time Force refresh of the site Browser automagically cleared the cache based on settings
  • Yahoo ran the experiment. Ran against an empty page
  • Older IE: 6 overall, 2 per host Older FF had 24 as overall and 8 per host Newer FF: 30 overall, 15 per host
  • Many host names = more DNS lookups, adds delay Consider the effects of CPU thrashing for the client Lookup times vary across ISPs and geographic locations
  • dynamically combine and cache Combine and minimize before a release
  • Don't use HTMTL attributes to scale Favicon – keep it around, keep it small

Transcript

  • 1. Frontend Caching The “new” frontier ZendCon – San Jose, October 2009
  • 2. Head of R&D at echolibre , pear extraordinaire, author and from Iceland Head of R&D at echolibre , pear extraordinaire, published author and an Icelander Who is Helgi ? Head of R&D at echolibre , pear extraordinaire, author and from Iceland
  • 3.  
  • 4.  
  • 5.  
  • 6.  
  • 7.  
  • 8. 80% of response time is spent downloading content
  • 9.  
  • 10.  
  • 11. “ It all depends on how we look at things, and not how they are in themselves.” - Carl G. Jung
  • 12.  
  • 13.  
  • 14. Key factor in performance Fewer HTTP Requests Easy to improve on
  • 15. Sent with static content Slow upstream speed Big cookies
  • 16. Cookie Size Response Time (Delta) 0 bytes 78 ms ( 0 ms ) 500 bytes 79 ms ( +1 ms ) 1000 bytes 94 ms ( +16 ms ) 1500 bytes 109 ms ( +31 ms ) 2000 bytes 125 ms ( +47 ms ) 2500 bytes 141 ms ( +63 ms ) 3000 bytes 156 ms ( +78 ms ) Times are for page loads on DSL (~800 kbps).
  • 17. Eliminate unnecessary cookies Keep sizes low Appropriate domain levels Set Expires date appropriately
  • 18. Be aware of max connection limits in browsers CNAME to point multiple sub domains to the same IP
  • 19. One domain = 2 Parallel connections
  • 20. Two domains = 4 Parallel connections
  • 21. Too many hostnames can cause complications 2 – 4 sub domains is a good average
  • 22. Combining 6 scripts into 1 eliminates 5 requests Challenges:
      • develop as separate modules
      • 23. combinations vs. loading more than needed
  • 24. JS does not comply with the parallel downloading rule
  • 25. script defer attribute is not a solution
      • blocks rendering and downloads in FF
      • 26. slight blocking in IE
    Solution: move them as low in the page as possible
  • 27. Crushes the files Strips out all cruft Voodoo magic
  • 28. JSMin Dojo Shrinksafe Packer YUI Compressor http://short.ie/compression-rates
  • 29. You can affect users download times
  • 30.
      Gzip can be used on
  • 34.
      Gzip should not be used on
  • 37. robots.txt favicon
  • 38. CSS Sprites favicon
  • 39. Badly optimized Thumbnails PNG can be compacted 50%, no quality loss OptiPNG
  • 40. Test on slow connections Slow proxies for developers
  • 41. Data served through a single domain Smart routing software Data closer to the end user – Less latency
  • 42. Amazon CloudFront
  • 43. Appropriate dates Cache far in the future Change file names on releases
  • 44. Firebug Firecookie Yslow Hammerhead http://stevesouders.com/hammerhead/
  • 45. “ Knowledge rests not upon truth alone, but upon error also.” - Carl G. Jung
  • 46. Questions? Email: [email_address] Twitter: @h http://joind.in/talk/view/893