We have a new Drupal website at www.contentrealtime.com On our test site (not yet moved to live BETA) we have now added 160,000 records to our MySQL database in the form of eBook data elements (that can be searched, displayed and purchased). We have run into serious "SLOW PERFORMANCE" issues, both the main page of the site and any search we do. Any thoughts on how to tweak indexes or have Drupal respond reasonably to such a database record size? The Admin shows all items are indexed. Anyone sized a server to run this type of database with a Drupal website?

Respond to jim@contentrealtime.com or jduster@yahoo.com

Thanks!

Comments

minesota’s picture

subscribed

cog.rusty’s picture

Your problem seems very serious considering that the site is not even under any load yet. I wonder what happens under load.

There are quite a few performance related articles here: http://2bits.com/contents/articles . Maybe seeking the services of a proved specialist makes more sense than trying to apply random suggestions from here (not that it hurts).

Jax’s picture

160k database records really isn't all that much if properly indexed. It all depends on the server hardware running it. You should provide your specs, mysql configuration, "show variables" and "show status" details as well as the details of the mysql data folder to see the sizes of the index files. Then you also need the whole database structure and the contents of the slow_query log to see which queries can be optimized.

This is a nice intro to MySQL optimization:
http://www.interworx.com/forums/showthread.php?p=2346

Also it could be that the issue is not the database but an error in the code. So you might need to audit your code as well.

jduster’s picture

We are still experiencing 1-3 minutes to get a search result when using Drupal, with a database of about 160,000 records but tables with over 6 million records. Is this normal? How can we speed up searches?

You can experience our searches on www.contentrealtime.com, it is working fine with just some external XML searches and not much other than just a few local database items. But on our test server when we loaded about 160,000 records into the mySQL database (and the related tables, which makes for millions of rows) we are experiencing LONG search times.

Thoughts?

Anyone sped up a Drupal search before?

We are running on KnownHost in the production environment, in test environment it is Here are the HW summary of the test system:

1. Model: Dell Latitude D600

2. RAM: 1.0GB 333MHz

3. CPU: 1.8GHz

4. HDD: 20GB, 4200rpm

Thanks for any help or advice

Contact jim@contentrealtime.com

Jax’s picture

The first thing that seems odd is "4. HDD: 20GB, 4200rpm". For a database server I/O performance is important and as your database grows its importance also grows. For a database server you usually opt for RAID10 on a good controller with performant discs. 4.200 RPM is really slow. Yet a correct configuration is even more important!

The same questions as before still apply. Does anything show up in the slow-query log? What is your configuration?

You could also try http://drupal.org/project/apachesolr in stead of the standard search.

Another popular alternative seems to be http://www.sphinxsearch.com.