Optimizing Drupal Performance (English)
3 likes2,324 views
This document provides a checklist of 19 basic practices for optimizing Drupal performance. It identifies reasons for slow Drupal sites like full page renders and serving dynamic content to anonymous users. It recommends limiting modules, writing efficient code, caching, database tuning, web server tuning, and separating code and media. It asks for other optimization techniques that could be used.
Optimizing Drupal Performance (English)
- 1. Optimizing Drupal Performance Basic practices by Tim Kamanin @timonweb timonweb.com mailto:[email protected] Drupal Trójmiasto 3drupal.pl
- 2. Reasons why most Drupal sites are slow: - full page renders - serving dynamic content to anonymous users - slow mysql queries - module bloat
- 3. Typical Drupal Stack CSS / JavaScript Media Drupal Apache MySQL PHP Linux
- 5. 1. Limit number of your modules
- 6. 2. Always check what installed modules are doing behind the scenes
- 7. 3. Architect the system and write modules with performance in mind
- 8. 4. Split code invoked via urls into separate files: module_name.admin.inc, module_name.page.inc, etc
- 9. 5. use drupal_static(), provides central static variable storage, docs: http://bit.ly/QD86rP
- 11. 7. Export views and Panels to code
- 12. 8. Enable css / javascript aggregation
- 13. 9. Let aggregate cache to take care of css/js aggregation
- 14. 10. Enable page and page compression (mod_deflate)
- 15. 11. Install Boost to make anonymous caching 10 x times faster!
- 16. 12. Enable views and block caching for authorized users
- 17. 13. Store cache in memory. Install memcached or redis
- 18. 14. Cache PHP with APC
- 19. 15. Tune MySQL: - find slow queries - use indexes - use EXPLAIN on queries - tune my.cnf - get decent query cache and key buffer
- 20. 16. Tune Apache: StartServers MinSpareServers MaxSpareServers MaxClients KeepAlive
- 21. 17. Remember about mod_expires ExpiresActive on ExpiresByType image/jpg "access plus 1 month" ExpiresByType image/jpeg "access plus 1 month" ExpiresByType image/gif "access plus 1 month" ExpiresByType image/png "access plus 1 month" ExpiresByType text/css "access plus 1 months" ExpiresByType application/javascript "access plus 1 months"
- 22. 18. Separate Media and Code: - Move media to CDN - Move media to separate server
- 23. 19. Move search from Database to Solr search_api + Solr
- 24. What else can be done?
- 25. varnish, squid, load balancing, memcached, fields in mongdo, css sprites, Etag, ESI, separate database server, optimize media, preload, postload, external js, nginx, Lighttpd, amazon cloud, SSD
- 26. Comments, questions? @timonweb timonweb.com mailto:[email protected]