Too many SQL Queries – Extremely slow wordpress site

Thank you Chip. Here are the results:
The page got an overall Page Speed Score of 78 (out of 100)

High priority.
Leverage browser caching, Combine images into CSS sprites

Medium priority.
Defer parsing of JavaScript, Minimize redirects, Specify a cache validator

Low priority.
Minify JavaScript, Minify CSS, Optimize images, Minify HTML, Optimize the order of styles and scripts, Serve scaled images, Put CSS in the document head, Remove query strings from static resources, Specify a Vary: Accept-Encoding header

As you’re having a heavy WordPress site with many plugins on a dedicated server, it would be well worth the effort to optimize your server and analyze what exactly causes those queries that are inefficient.

As a first step, benchmarking your site (or a copy of it) with the default theme and with all the plugins disabled should give you an idea of the difference your plugins and theme make, then you could enable them one by one and see how the performance is affected.

As a reply to my earlier post, you wrote that you’re already using the W3 Total Cache plugin, but then you mention the WP Super Cache plugin in your list of plugins. If you had used one of these plugins first and then switched to the other one, you might need to check if it’s working properly.

Thank you for your reply! I had W3 but after my reply I deactivated and activated the WP super cache. I have to admit that the site is more responsive now but there are still some hiccups! I need to locate the problem and eliminate it. Something causes these queries and let them stay alive and overload the server… please help me… I’ve moved to a bigger dedicated server from a vps to solve the problem but the problem persists. hence it’s not a problem with the server. It’s in the wordpress!

Can anybody please help? I found out that when a new post is published then everything collapses and queries overload the entire server!

If that helps, what still overloads the server is these:

| 106066 | user | localhost | blog | Query | 6 |
Copying to tmp table | SELECT wp_terms.slug, wp_posts.ID,
wp_posts.post_name, wp_posts.post_title, wp_posts.post_author |

| 106072 | user | localhost | blog | Query | 3 |
Copying to tmp table | SELECT wp_terms.slug, wp_posts.ID,
wp_posts.post_name, wp_posts.post_title, wp_posts.post_author |

| 106073 | user | localhost | blog | Query | 2 |
Copying to tmp table | SELECT wp_terms.slug, wp_posts.ID,
wp_posts.post_name, wp_posts.post_title, wp_posts.post_author |

| 106075 | user | localhost | blog | Query | 1 |
Copying to tmp table | SELECT wp_terms.slug, wp_posts.ID,
wp_posts.post_name, wp_posts.post_title, wp_posts.post_author |

| 106076 | user | localhost | blog | Query | 1 |
Copying to tmp table | SELECT wp_terms.slug, wp_posts.ID,
wp_posts.post_name, wp_posts.post_title, wp_posts.post_author |

| 106079 | user | localhost | blog | Sleep | 0 | |

You should check your MySQL server configuration with a tool like mysqltuner.pl (https://mysqltuner.pl/) or tuning-primer.sh (https://forge.mysql.com/projects/project.php?id=44) to get an overview about your current configuration and some ideas for improvements.

The queries you’ve shown here aren’t complete, so besides the fact that MySQL has to create a temporary table to execute them, there’s not much I can say. Try to determine which script causes these queries first, then you can debug it.

I am having the very same issue with fatcow for my blog.
The Nerdy Nurse

It started happening randomly without me installing any new plugins or changing any code

I am in tension i am unable to fix the problem in https://basecamptrekking.com/ plz any one solve my problem

But then gain no one actually has a solution?
Wp is creating tmp tables causing the delay, the creation of these tables max out i/o disk and after a while the process remains running forever and oocks. i have a quadcore with 16G dedicated server. I guess this comes with using wordpress as a script??

@pimpwise: As you’ve got plenty of RAM, you could look into moving the directory where MySQL stores its temporary tables to a “tmpfs” volume. This can make a big difference, as writing the temporary tables won’t hit the disk anymore.