Have you come up with the next big thing? Coding it is something every new startup faces but what happens when it really does becomes the next big thing and servers start to crawl under the load? In this workshop we'll cover a number of ways to identify bottlenecks and how to solve them once found. We'll also cover how to perform some extra scaling without expensive hardware. * Benchmarking (f.ex. ab) * Profiling with Xdebug * Memcache * APC * and various other caching methodologies Hopefully this will prevent you from becoming the next failwhale.

1. Caching For Cash php|tek – Chicago, May 2009

7. 80% of response time is spent downloading content

10. “ It all depends on how we look at things, and not how they are in themselves.” - Carl G. Jung

13. Key factor in performance Fewer HTTP Requests Easy to improve on

14. Sent with static content Slow upstream speed Big cookies

15. 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).

16. Eliminate unnecessary cookies Keep sizes low Appropriate domain levels Set Expires date appropriately

17. Be aware of max connection limits in browsers CNAME to point multiple sub domains to the same IP

18. One domain = 2 Parallel connections

19. Two domains = 4 Parallel connections

20. Too many hostnames can cause complications 2 – 4 sub domains is a good average

22. combinations vs. loading more than needed

23. JS does not comply with the parallel downloading rule

25. slight blocking in IE Solution: move them as low in the page as possible

26. Crushes the files Strips out all cruft Voodoo magic

27. JSMin Dojo Shrinksafe Packer YUI Compressor http://short.ie/compression-rates

28. You can affect users download times

30. CSS

31. XML

32. JSON

34. PDFs

35. Compressed data formats

36. CSS Sprites favicon

37. Badly optimized Thumbnails PNG can be compacted 50%, no quality loss OptiPNG

38. Test on slow connections Slow proxies for developers

39. Data served through a single domain Smart routing software Data closer to the end user – Less latency

40. Amazon CloudFront

41. Appropriate dates Cache far in the future Change file names on releases

42. Hash tag to compare between browser and server Gives more flexibility than last-modified-date Great on a single server setup

43. Typically unique to a server Disable if not being used!

44. Use options that are not unique per server

45. Firebug Firecookie Yslow Hammerhead http://stevesouders.com/hammerhead/

46. “ Knowledge rests not upon truth alone, but upon error also.” - Carl G. Jung