Why Bad Coding Can Crash Your Server

on Wednesday, November 2, 2011

Lately I have realized why clean code and being compliant with the W3C Markup is so important. Currently we have one site doing colse to 25,000 uniques a day, which commonly isn't very much. However, the script it is running on was a modded turnkey which was nothing pretty to begin with.

The script calls images and other facts straight through mysql databases and it's gotten to a point that at peak hours (9pm -11pm) the site has managed to crash the server at hostgator three nights in a row.

Cloud Vps

I hear you saying now, hostgator web hosting is crap and that's the reason... Well I'd believe it but I have an additional one server with hostgator that can deal with that kind of traffic no problem, and it's less costly than the dedicated server that keeps crashing. It is all to be blamed on the script, which will remain nameless (not that it matters though, they already terminated up shop and released "version 2.0″ under a new company name.

Always make sure you are working with scripts that can deal with high traffic once you get there, and a good episode to be learned from my experience is to start off with a institution script that does everything you want before you start instead of using a turnkey and trying to mod it yourself.

Again, I will have to move this site off the server and whether scrap the script altogether or duplicate two servers and balance the load. whether way, learn from my mistake and don't make the same one.

Why Bad Coding Can Crash Your Server

0 comments:

Post a Comment