By aharown07 on

Developed my first ever Drupal site over the last several months. Everything seemed to work fine in a subfolder of my public_html. When I tried to go live with it, though, it began to hit very high mysql queries per second (so they host folks tell me), resulting in heavy cpu and eventually tipping over the mysql service.
So... site quickly dies after restarting mysql.

- host = virtual private server at inmotionhosting ... 256 RAM ... bunch of pretty decent cpu's
- robots.txt was the drupal default, but when trouble started (and host co reported heavy crawler traffic), added an exclude all to it.... no change observable

Yes, my site is heavy... acl, forum access, lots of views, more than 200 tables (a bunch of which are sitting empty from modules I decided later not to use). Bells and whistles galore (that's why I went to Drupal!)

But we were maxing out the cpu's at 3AM in our main user time zone... with pretty much nobody logging on.

So... any ideas what might be doing this? Host co says go dedicated server. Is that overkill?

⋅ Categories: Drupal 6.x

Comments

fluxrider’s picture

fluxrider commented

What do you logs tell you ? Should be lots of recent log entries. They will give the clue to whats going on. You'll find them in admin - logs
Is it pure drupal or do you have embedded apps in there ? what version drupal mysql

dedicated server hehe. What site are you running ? I think you should also ask host for next vps plan that offers more than 256mb of dedicated memory, which I think is a bit low imho - good for dns domain server

Bobby1290’s picture

Bobby1290 commented

Install and enable the http://drupal.org/project/devel. Then see which queries are the ones that are running with no (user)load.
Repost here if you can't figure out where those queries come from.

As a side note, don't just disable modules you are not going to use, uninstall them as well.

Good luck.

aharown07’s picture

aharown07 commented

Thanks! I should have come back and posted here sooner.
Turned out that I had introduced some corruption of some sort in the database during my migration efforts. Never was able to determine exactly where those were but when I returned to a pre-migration version of the database, everything was normal again.
I am still getting alot of 404's in the logs (a whole lot of something is looking for pages/files that no longer exist... we migrated from wordpress an vbulletin to drupal. I don't know if these are crawlers that don't yet 'know' the old site is gone or what).
But these do not seem to be putting much drag on the server now.