3 ms·

It's more than likely Drupal related! Front end cache would have helped there.

by babysteps 13y ago

kitsune_ 13y ago
Are you insinuating that Drupal lacks page caching? Because that would be a patently false statement.
- drawkbox 13y ago
  Without cache, Drupal would never run as it drinks database connections in the hundreds per user request.
  - rjknight 13y ago
    "Hundreds per user request" is just wrong. Generally, Drupal opens a single connection per request (and does not use any kind of connection pooling). Perhaps you mean that Drupal issues hundreds of queries per connection? (Which is definitely much closer to the truth).
    - drawkbox 13y ago
      Yes I was going overboard but indeed it is truly hundreds of queries and sometimes numerous connections per user. Some sites I have had to deal with on initial inspection have 250+ queries per user (sometimes the same ones over and over due to plugins/modules) and people wonder why after 10 users it breaks the database/site. Without cache on wordpress you might be in trouble, without cache on Drupal you don't run. Still, Drupal is orders of magnitude more useable than other PHP frameworks like Joomla. The PHP that is fun is using microframeworks like limonade, flight etc if PHP is used.
- rjknight 13y ago
  No, but Drupal's out-of-the-box page cache caches pages in... the database. Even with pages cached in Memcache, Drupal would open a DB connection by default (it's possible to override this using page_cache_without_database, but not everyone is going to do that). Using something like Varnish as the primary page caching mechanism would work around this, albeit with some trade-offs. Generally though, the fault with issues like this is often that the MySQL connection limit is set lower than it needs to be. Often, this is set at a level far below that which would actually cause the DB server to become overloaded, and it just starts rejecting further connections even if capacity exists to handle more. EDIT: typos
babysteps 13y ago
I chose my words carefully. Not wanting to get too technical. I was not insinuating that Drupal hadn't it's own caching. Page runs on Drupal > Drupal uses database > Database connections were exhausted. I was suggesting caching up front to bypass calls to the database (not specifying a particular piece of caching software). At the time I was looking at the page through a 3rd party cache. I didn't realise the page had inline comments, those would of course complicate the problem.

It's more than likely Drupal related! Front end cache would have helped there.

kitsune_ 13y ago

Are you insinuating that Drupal lacks page caching? Because that would be a patently false statement.

drawkbox 13y ago
Without cache, Drupal would never run as it drinks database connections in the hundreds per user request.
- rjknight 13y ago
  "Hundreds per user request" is just wrong. Generally, Drupal opens a single connection per request (and does not use any kind of connection pooling). Perhaps you mean that Drupal issues hundreds of queries per connection? (Which is definitely much closer to the truth).
  - drawkbox 13y ago
    Yes I was going overboard but indeed it is truly hundreds of queries and sometimes numerous connections per user. Some sites I have had to deal with on initial inspection have 250+ queries per user (sometimes the same ones over and over due to plugins/modules) and people wonder why after 10 users it breaks the database/site. Without cache on wordpress you might be in trouble, without cache on Drupal you don't run. Still, Drupal is orders of magnitude more useable than other PHP frameworks like Joomla. The PHP that is fun is using microframeworks like limonade, flight etc if PHP is used.
rjknight 13y ago
No, but Drupal's out-of-the-box page cache caches pages in... the database. Even with pages cached in Memcache, Drupal would open a DB connection by default (it's possible to override this using page_cache_without_database, but not everyone is going to do that). Using something like Varnish as the primary page caching mechanism would work around this, albeit with some trade-offs. Generally though, the fault with issues like this is often that the MySQL connection limit is set lower than it needs to be. Often, this is set at a level far below that which would actually cause the DB server to become overloaded, and it just starts rejecting further connections even if capacity exists to handle more. EDIT: typos

babysteps 13y ago

I chose my words carefully. Not wanting to get too technical. I was not insinuating that Drupal hadn't it's own caching. Page runs on Drupal > Drupal uses database > Database connections were exhausted. I was suggesting caching up front to bypass calls to the database (not specifying a particular piece of caching software). At the time I was looking at the page through a 3rd party cache. I didn't realise the page had inline comments, those would of course complicate the problem.