Take the 2-minute tour ×
WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. It's 100% free, no registration required.

So I have a really large woocommerce site (partsboss.co) that has around 83,000 items. It's on VPS hosting with digitalocean, and things were running super fast until around 50,000 items. Now the site is just draaaaaaaaaging.

It's set up on Ubuntu with nginx, APC and Varnish caching. I'm not really sure where the bottle neck is or how to fix it, but as far as I can tell it's basically taking forever to query the mysql database and return results.

So my question is, do I need to just optimize mysql more (if so, how? Not really a mysql expert) or do I need to split the database with something like Hyperdb? Again, if that's the case, I read the readme for Hyperdb and it wasn't too explicit... if you know of any good tutorials, throw them my way :) Any help would be much appreciated, thanks!

share|improve this question

closed as too broad by toscho May 24 at 13:30

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.

1  
Do you have debugging information? What do you see in the server logs? You will probably need to enable MySQL Slow Query log for the debugging. –  s_ha_dum Oct 30 '13 at 14:22
    
have you done any of this brainstormcreative.co.uk/website-design/… im at 26k products en route to 200k+ and having same issues –  user43757 Dec 11 '13 at 8:40
    
I have noticed that since WP3.6 the new admin-ajax.php has been hammering the database. Due to the new heartbeat 'feature.' Profile your plugins and see which ones are eating db time. –  Digitalchild Dec 11 '13 at 22:26

1 Answer 1

Did either of you solve your issues with Woocommerce being slow?

After some profiling, I determined it was PHP being slow, not SQL.

Total query time: 0.05915s for 89 queries.
Page generated in 22.00653s (99.73% PHP, 0.27% MySQL)

With that info, nothing you change in the front end is going to solve anything.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.