Drupal can be a resource-intensive system. Any moderately complicated site will generate a lot of database queries and use a fair amount of memory to build pages to serve to visitors. With some judicious tuning, however, Drupal can perform really well, and at scale.
In this webinar, Drew Webber, Principal Support Engineer at Acquia, will discuss some common pitfalls encountered by sites that struggle in the face of increased traffic. Attendees will walk away with a deeper understanding of:
-The most common problems encountered when it comes to Drupal site performance
-Ways of identifying performance bottlenecks on your Drupal site
-How to avoid these common pitfalls and remedy these issues (often without writing a single line of code!)
-What not to do when building and running your site
13. Don't forget to...
● Set up Fast404
○ (partially built in since D7)
● Load test
○ practice failing
● Plan for growth / expansion
○ e.g. organisation of files directory
14. 404 handler
# Pass all requests not referring directly to files in the filesystem to
# index.php. Clean URLs are handled in drupal_environment_initialize().
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !=/favicon.ico
RewriteRule ^ index.php [L]
15. What not to do
● Blocking external call (in eval’d PHP stored in the db, to a dyndns host)
● Hacking core (badly)
● variable_set (see cache_debug)
● debugging left on / error_reporting off
● drupal_add_js() with a timestamp
● nuke cache from orbit
● expensive 404s
● PHP filter for anon
● one way ticket releases