Hey friend,

Great topic! I want to say something that I said in another thread recently, because I believe that I have experience that applies to necessary expectations. I like to start here and work backwards.

I have never witnessed a WooCommerce site that had been running for a while, grew over time, and performed well. I don’t think it’s the fault of anyone, I think Wordpress is a bad platform for e-commerce at scale, and I think that you can outgrow it to the point that your efforts to sustain it become far too high as opposed to using a platform that was made from the ground up to support e-commerce. I used to do a lot of managed Wordpress work, in which I would find myself migrating websites to VPS and dedi from shared hosting, for the purpose of improving performance. Sometimes the application itself made the job impossible.

Now, let’s talk less about my negative experiences and more about what I might try to improve it. You can’t give up before trying. In a lot of the cases I dealt with, the primary problem was that you just can’t cache all content all the time on an e-commerce site. You have to hit the database, it’s just not a blog. So my thoughts are these:

1. Try 4x web and 2x MySQL servers in master-master replication. I’m thinking: 4x 2GB standard droplets for web, 2x 4GB standard droplets for MySQL.
2. Clean house with plugins. If you have to think for more than 5 seconds about why you need it, get rid of it. Extra emphasis on security plugins, you can have security without weighing down the web app and database further (some of these write visitors to a plugin-specific table, meaning zero web sessions without a matching MySQL session, rendering caching effectively useless).

I don’t really think you need CPU optimized unless something is broken on the site, and that is the angle I would approach it from. If you need it, a plugin is probably causing more activity than needs to occur. It should take almost no processing power to serve a cached page.

Jarland