Drupal Memory Performance

Drupal has been known to be quite resource intensive, but I'm happy to hear about the improvements that are being made for Drupal 8. I just wanted to share this interesting post I found on Drupal and the PHP Memory Limit:

Why does Drupal need so much memory? Among other things, because it has a cache problem (which of course saves your database) Drupal currently likes to cache ALL views in one place, ALL fields in one place, etc. So once you get a site with many content types, fields, views, the caches become huge, and they are all loaded into your memory with each request.... [read more]

Introduction to Using Drupal Cache

For anyone that stumbles on my site, I thought I would share this helpful article from Lullabot on A beginner's guide to caching data in Drupal 7.  I found it both interesting and useful.  I hope that it will be enlightening to you as well.

Building complicated, dynamic content in Drupal is easy, but it can come at a price. A lot of the stuff that makes a site engaging can spell 'performance nightmare' under heavy load, thrashing the database to perform complex queries and expensive calculations every time a user looks at a node or loads a particular page.
...because page level caching is an all-or-nothing affair, it only works for the standardized, always-the-same view that anonymous users see when they arrive.
Eventually there comes a time when you have to dig in to your code, identify the database access hot spots, and add caching yourself. Fortunately, Drupal's built-in caching APIs and some simple guidelines can make that task easy.