By denverrusty on

I have a website that has been created using Drupal. The test site is at http://dodsonmediaservices.us. I have tried installing this on numerous servers and hosting companies to try to determine whether it is a server environment problem or a problem caused by Drupal / Drupal installed modules / theme modifications. The problem is happening on all servers after the site has been used for a while. The site becomes painfully slow and it is affecting other applications on the server. A restart of the server clears it up for a while but it gradually slows to a crawl again. I am not sure how to quickly determine the culprit. I have tried uninstalling some modules but that hasn't fixed it. The database doesn't appear to be the problem The access speed seems to be good. Maybe there is a memory leak somewhere or something else that is causing the server to gradually become slow. I would like to find someone quickly to assist.

⋅ Categories: Drupal 5.x

Comments

antgiant’s picture

antgiant commented

Installing and enabling the Devel module (http://drupal.org/project/devel) will allow you to see which if any sql queries are slowing everything down. A complete shot in the dark however would say that it sounds like you have a very active site and have set watchdog to store logs for to long. You can also do things like run top/Task Manager to determine exactly which processes are using up your cpu time if you have access to them.

kavimclansys’s picture

kavimclansys commented

We can help you certainly..We are the strategic partner for the largest linux distributor for UK. we take care of all drupal implementation for linux community

hit me in skype my skype id is sri.kavi

With Regards,
kavitha.S
SKYPE :sri.kavi

kbahey’s picture

kbahey commented

From your description, it may or may not be Drupal related.

You say it is cleared by a server restart, so perhaps it is memory usage per Apache process? To rule that out, look at the tools for performance tuning and optimization, and check how much each Apache process takes as resident memory.

If it is indeed the size of Apache process that is the culprit, then perhaps you have fell for the server indigestion and the Drupal contributed modules open buffet binge syndrome, and you need to find out which module(s) are the ones that are most memory hungry.
--
Drupal development and customization: 2bits.com
Personal: Baheyeldin.com

--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba