Geek Alert! Geek Alert! Geek Alert! That’s my way of saying Jon Olson stop reading you’ll bore yourself to death but please till retweet anyways!
The past few hours I’ve been unlearning or relearning a tactic I’ve been using to make things faster. Turns out, you can make it slower by making it faster. Understand that? Neither did I.
So let’s get the story started. Well, we use a super cluster for our hosting. It’s a rock solid, never goes offline type cluster. Super cool right? Well a few days ago I noticed it was starting to act slow*. In fact, everyone did. Not cool.
Come to find out, I’ve been using APC Cache in PHP. Well I was actually over using it. It was slowly eating up RAM in our web servers, and maybe even leaking it. I know in the past bug fixes said it did it, I don’t know if it was or not (I’m not that nerdy). Anyways, all this time I’ve been using it to the max not realizing how much RAM it was using up. And funny enough our cluster is so fast it’s faster NOT using it.
So now I get to go through all the code and decide which places to remove it. Yay! It’s actually not been that bad, but every single time I find it used and I have to rewrite code it’s like a huuuge reminder it was my bad! Thankfully our server people are super cool and don’t get upset when we get on the phone with them and have conference calls with their team only to find out it was me.
The moral of the story I guess is to keep an eye on *EVERYTHING*. Especially when you keep growing like we are, the slightest changes can have the craziest effects. We’re up to 1,330 queries per second on our DB server now. Huya!
*Disclaimer: I put it at the bottom because Jon’s not gonna read this far, but he did tell me it was acting slow a week or so ago but I didn’t notice it so I thought it was silly Canadian internet speeds. I mean c’mon Canada, you should have 31/21 innernets too..