Deprecated - Performance and scalability

I want to know how many queries Drupal executing when a page (specifically front page).
I have production site with 28k nodes, so I can't install devel module.
Pls suggest optimisation techniques.
------
Sharique

I have a biz where I am hosting my customers on a VPS server running http, exim, pop3, imap, mysql, etc (basically, all processes). I'm running multi-site
As the users are independent of each other, I thought I'd give each user a different DB and simply copy the contents from my master DB when I create a new site.

So far I have no problems, but I only have a handful of sites and they're currently pretty low volume.

What happens when sites grow to dozens and hundreds and / or volume goes up?

I have a 5.1 Drupal site with about 7000 nodes. When I started to index the site (using cron.php) everything seemed to work pretty well at the start. I was indexing about 100 nodes per cron run with no problems.

After several runs of cron, I started to get timeout errors (240 second timeouts) from php, so I reduced the number of search items to 50. Everything worked well for some time again and then I started to get the timeouts again. So I then reduced it to 20. Again, everything was happy for a while, but then, I started getting the timeouts. I reduced it to 10 - same thing happened again - after about 10-20 runs of cron.php, I started getting the timeouts.

So I can no longer run cron.php at the lowest setting (10) without getting the time outs. There are still 771 nodes to index (89%) but so far, I can't get any more to index no matter how many times I run cron.php (and time out).

I went through the database tuning documents to make sure I had things set up correctly. I'm using MySQL with the innodb engine (as recommended), query caching is turned on with a 16MB cache size. I've "optimized" the search_* tables. I've turned on query logging (both regular and slow queries). I've isolated the site so that no other operations are occuring other than the search indexing within cron.

Hello,

We had our first customer running a Drupal site make the front page of digg.com yesterday and have some interesting observations. My hope in posting this thread is 2 fold - 1) to provide some information to users of Drupal on how to better optimize their install and 2) provide some feedback to the drupal development team.

First off, we run a clustered environment, where all services are separated onto dedicated resources (so, control panel, dns1, dns2, web, email, mysql, etc) are all located on separate servers.

As soon as our clients site (www.medopedia.com) made the home page of digg.com, our server loads sky rocketed. The link to the digg.com reference:

http://digg.com/health/6_Common_Myths_about_Sleep

Server Specifications:
Web Server - Dual Xeon, 4 GB RAM, SCSI Drives, baseline load average (before digg effect) = 0.50
MySQL Server - Dual Xeon, 8 GB RAM, SCSI Drives, baseline load average (before digg effect) = 0.20

As soon as the site was featured on digg.com, the web server load shot over 40 (effectively rendering service unavailable) and the mysql server load increased slightly.

cache was already enabled on this site. However, adding the following directives (gzip) to .htaccess reduced the load of the web server to below 6



mod_gzip_on Yes
mod_gzip_dechunk Yes

How can a webmaster update their Drupal web site without disrupting service?

If availability is not important, a webmaster may modify the code in-place, taking the site offline for a several hours while update scripts are run and last-minute bugs are fixed. Otherwise, if multiple servers are available, another set of solutions arises.

What follows is an outline for managing concurrent versions of a single web site and for switching the active version. The outline assumes a shared hosting environment with access to a unix-type filesystem.

Perhaps that sentence alone is enough to trigger ideas in the minds of experienced Drupal multisite users. But if you want more details, read on!

The use of jQuery can cause serious performance problems in pages. If your pages are slow and you use jQuery, try telling your page not to load jquery.js and see what the effect is.

Not sure not what the remedy is, but do not think this is a Drupal-specific issue. However, many Drupal people are happily jumping on the jQuery bandwagon and they should realize there is no free lunch.

Here are two links to Google groups discussions on the issue of jQuery performance: