1. Magento server & environment optimization Get very fast page rendering, even under heavy load ! E-commerce is also about

3. French managed hosting leader on Magento

4. 500+ Magento site running

5. Playing with Magento since August 2008

6. French community leader (Bargento, Wikigento, etc.)

7. Specialized in Magento performances2

9. How to measure what really count ?

10. What contribute to load time ?

11. Why Magento is resource Hungry ?3

14. Graph (given by Google) show clearly the target: 1.5s

15. More and you are part of the red team called « SLOW »

16. This is not good for your SEO ranking and SEM efficiency

17. Relevance is still more important but… Don’t you have competitors ?Our goal is now clear : load in less than 1.5 second

18. What contribute to load time ? This and, of course, network transfers.

19. What contribute to load time ?

21. Do it in assembler, it will be fast and you’ll become crazy

22. The use of OOP language & framework help to work faster

23. PHP is still an interpreted language (Vs Compiled one)

24. Magento is a kind of “meta” framework

25. The EAV model gave a lot of flexibility to the catalog but is costlyGive me CPU & RAM and you’ll be able to use a framework instead of coding all by yourself

27. Funkload

28. Yslow, Pagespeed & Gtmetrix

29. Realistic goals to reach9

32. Tolerating (from 1 second to 4 seconds)

33. Frustrated (more than 4 seconds)

34. Inacceptable (not served/errors)1,00 0,94 E G 0,85 F 0,70 P 0,50 U 0,00 Tolerating count Satisfied count + 2 APDEX = T Total samples

36. It provide reliable tests and cute reporting capabilities

37. Allow you to draft scenarii and inject them

39. www.gtmetrix.com does it directly through a site (thus 4 all browsers)

40. Reaching more than 90% is not easy, a default demostore, on a default serveur (no optim) scores C/C (76/72%) and takes ~3,1s to load.

41. Those two performance rule set are among the most complete

42. Respecting all rules will grant you a serious SEO & perfs boostIt is mainly not Magento’s task to take care of this but your hosting company should !

44. 45 ms to get the home and start downloading the static files

45. Grade A/A on Yslow & Pagespeed

46. Deliver massive parallelizing and caching capability

47. Serving up to 200 simultaneous actions (~50 000 Uniq visitor / day) per front web servers with a Community Edition

48. Serving up to 300 simultaneous actions on a Enterprise Edition (FPC)This is not a dream, this is called engineering & optimization

50. Where to act ?

51. Sizing your architecturehttp://fr.fotolia.com/id/7005820 14

53. Forget to activate Bloc Caching

54. Badly coded Crons

55. “Cold cache” effect

56. Load a lot of products/categories on the Home

57. Let the Log database be overcrowded

58. Foreign includes

59. Misconfiguring Magento’s cache setting

60. Conception errors (like real time sliders)

61. Hard disk access, nothing worseUsually it’s the small errors, the temporary fix, that wreck havoc

62. Where to act Webserver Integration / Extension Tuning / Settings Environment More than 16 points to act on, it’s no small duty.

63. Sizing your architecture Large Medium Small Extra Large Mutualized Virtualized 0 to 2000 UV/d Dedicated, Separate W/DB ~30 000 UV/d Dual Datacenter Load balanced ~80 000 UV/d Dual Datacenter CDN + Cloud for pikes > 100 000 UV/d UV/d = Uniq Visitor per Day

65. Advanced optimization tricks

66. Top optimization tricks

67. Nitrogento18

69. Activate Flat catalog

70. Use Enterprise Edition (full page cache)

71. Activate Mage_optimizer

72. Use SOLR for large catalog

73. Opcode caching system (APC, Zend, Eaccel etc.)

74. Activate caching in back office (and check that code calls it)

75. Minify & compress JS & CSS files (Nitrogento does it)

76. Tweak your apache config (Use Etags, Expire headers, Gzip)Simple but yet efficient.

78. Put cache & sessions files on ramdisks

79. Split Front / Back Office instances

80. Use IRQ Balancing

81. Mount disk with noatime option

82. Lower socket Wait Timeout in /proc

83. Add a reverse proxy (Nginx or Varnish for example)

84. CDN get resources from many different CNAMES

85. Truncate (or archive) your log tables in Magento

86. Check foreign includes response times and put them at the endA bit tricky but will help.

87. Advanced optimization : Focus CDN 8 resources per servers, 32 resources in one run ! CDN / media servers are good for load time. 8 resources, then the next 8 resources, etc…

89. HTML5

90. Progressive degradation

91. Sprites

92. Deactivate atime

93. Tune up your DB

94. Try Nginx + PHP FPM (warning, no htaccess support)

95. Use DRBD to link two servers (blockdevice across network)

96. Latest Memcached + memcache client => flush the old cache keysGet the most out of the technology, fine tune, upgrade to latest, enjoy !

101. USA

102. Asia

103. Spain

104. SwitzerlandNeed (fast) Magento managed hosting ? www.nbs-system.com (soon available in English) Telephone : +33.1.58.56.60.86 Mail : phu@nbs-system.com