Optimizing Drupal Performance. Tips and Tricks
5 likes808 views
The document provides 20 tips for optimizing Drupal performance. It begins by introducing the author and defining performance as how long it takes to render a page on the server and in the browser. It then explains that performance is important for user experience and business reasons. The rest of the document details specific tips, such as limiting modules, caching content, tuning MySQL and Apache settings, offloading media, and using search optimizations. The overall message is that optimizing Drupal performance requires understanding tools, caching content, tuning server configurations, and separating code from media.
Optimizing Drupal Performance. Tips and Tricks
- 1. Optimizing Drupal Performance Tips and Tricks by Tim Kamanin @timonweb timonweb.com mailto:timur@kamanin.com DrupalCamp Wroclaw 2013
- 2. About me - Freelance Drupal consultant - Working with Drupal since 2006 - Started my journey from building own projects on Drupal - Share Drupal knowledge at timonweb.com - Co-founder of Drupal Trójmiasto Users Group (Gdańsk / Sopot / Gdynia, 3drupal.pl) - Creator of Dropbucket.org – Drupal snippets repository
- 3. What is Performance? Performance refers to how long does it take to produce a page. It is a result of how long it takes to render a page on the server and on the client side in the browser.
- 4. Why do we care about it? Performance is Love and Money
- 5. THE HORRIBLE TRUTH ABOUT DRUPAL IS ...
- 6. Photo by Chris Hoving
- 7. Drupal is ● Database intensive ● Memory intensive ● Can easily become a resource hog
- 8. Reasons why most Drupal sites are slow: ● doing full page renders ● serving dynamic content to anonymous users ● slow mysql queries ● module bloat aka „open buffet” syndrome
- 9. Typical Drupal Stack Linux CSS / JavaScript Apache MySQL PHP Drupal Media
- 10. Drupal Performance Tips and Tricks
- 11. 1. Know the Tools
- 12. Devel
- 13. Developer Tools in a browser
- 14. ● Pingdom ● YSlow ● Apache benchmark ● XHProf ● top / htop ● New relic ● mytop / mtop ● PhpMyAdmin ● And lots more Know the Tools
- 15. 2. Limit number of installed modules
- 16. 3. Always check what installed modules are doing behind the scenes
- 17. - take advantage of caching (drupal_static(), cache_set(), cache_get()) - split ui part and functional part - take advantage of Drupal's Ajax Framework - Use Drupal API!!! 4. Develop modules with performance in mind:
- 18. 5. Enable css / javascript aggregation: ● built in ● aggregate cache module
- 19. 6. Cache PHP with APC
- 20. 7. Export views and Panels to code
- 22. 9. Remeber, cache saves the cash! Cache everything!
- 23. 10. Enable page cache and page compression (mod_deflate)
- 24. 11. Install Boost to make anonymous caching 100 x times faster or play with Varnish and make things even faster!
- 25. 12. Enable views and block caching for authorized users
- 26. 13. Consider using ESI and authcache to cache pages for authorized users. WARNING: This solution is for experienced users.
- 27. 14. Store cache in memory. Install memcached or redis
- 28. 15. Tune SQL - find slow queries - use indexes - use EXPLAIN on queries
- 29. 16. Tune MySQL: Tweak my.cnf: - query_cache_size – caches query results (32M - 512M) - innodb_buffer_pool_size – caches indexes. Up to 80% of your memory - table_cache – number of tables mysql keeps in cache. Start with 1000 - tmp_table_size and max_heap_table_size
- 30. ● StartServers - number of child server processes created at startup (default 5) ● MinSpareServers - minimum number of idle child server processes (default is 5) ● MaxSpareServers – maximum number of idle processes (default is 10) ● MaxClients - maximum number of connections that will be processed simultaneously, otherwise queued (default 256) ● KeepAlive. On / Off depending on circumstances 17. Tune Apache:
- 31. 18. Separate Media and Code ● Move media to CDN ● Move media to separate server
- 32. 19. Move search from Database to Solr search_api + Solr
- 33. 20. Optimize, measure and repeat!