I have some good news and some bad news. The good news is that my website(s) are bringing in traffic, the load is spiking. No thanks to google - I am still on their terrorist list or whatever, so even when I'm directly in front of their faces they don't see me. But my sites are gaining popularity anyway.

And that's precisely the bad news. This week, all the traffic brought my shared infrastructure down, despire me not using any heavy machinery such as rails. All my content and marketing traffic is powered by php and javascript, both are lightweight relative to things like ruby on rails - and still, my database instance got overwhelmed.

I'm back to addressing performance issues like in 2012, when I first experienced this kind of difficulty. Only this time, I hope to address it, and not buck down under the load.

I'll be posting performance optimizations specific to Drupal and php/mysql stack here:  https://wiki.wasya.co/index.php/Drupal_Performance  It's nothing too exciting, it's not written as an article, it's just a list of things that I'm doing to improve performance. I'll be adding more to that list. For now though... I rebuilt the database and increased maximum number of connections, so at least the sites are up. Next on the list of things to do is better cache management. Stay tuned!

.^.