I wanted to see if anyone that runs Drupal in a reasonably active environment has the same concerns I do. It seems to me that Drupal inherently is a resource drain (trying not to offend anyone) but it is a beast. With every module you enable comes a plethora of new database activity.
Due to the application module each module you enable is loaded on the index page which is used for everything:
Website Hits:
1,000,000 per month
33,333 per day
1388 per hour
Database Activity:
150 queries (just a single hit to the homepage)
This seems like trouble to me! Obviously the fewer modules you use the better! But are there better ways of solving this issue? Or is this just the pitfall of the application model?
Anyone else running equal or more then 1M hits per month with great performance. It really hit us hard when we send out any mailers that create minor spikes in traffic (nothing serious 6K new visitors in a day.)
I’m running on 2 load balanced servers hanging off a central DB.
Thoughts other experiences?!?!
Cheers,
-p
P.S. just wanted to use "plethora" more then once. ;-)
Comments
Nobody else is worried about this....WOW!
Am I off base and this issue only exists for me, or nobody else really cares about this issue?
or
People who might relate missed it. To wonder if people didn't care, assumes that people interested in your issue read it. Perhaps more information might help.
As to db queries and their impact, that is always a concern, solutions or methods of solutions would also help.
There is a discussion proposed on one of the email lists about high volume sites. Unfortunatly, I don't remember which list. I also don't know enough abotu 'high volume' traffic websites to know if yours was one of them.
My busiest site only did 980MB traffic and just under 50,000 hits last month so I can't relate.
-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide