I've got a site that is starting to bog down my server due to the massive number of connections it's getting all day. It hosts an extension that runs in 4 different browsers, and the only way I can keep a simultaneous release schedule is to host it myself rather than submit to each browser's "gallery"...
Currently, I'm doing about 4.5gb of outbound traffic every single day from this site. I realize that's not legit level insane - it's nowhere near on the scale of a big company's idea of "lots of traffic", but it's enough that my colo server (that hosts some database intensive sites, as well) is starting to get irritable.
Problem is, all the update check requests and the increased popularity (thus tons of downloads) mean that my server almost always has 100+ connections going at a time.
I don't have much budget, and I barely get donations for this extension, so I'm trying to figure out a solution I can afford to keep providing it to the masses...
I'm looking at Linode, who I've used for lightweight stuff before, and I'm worried that a 512mb Linode just isn't enough RAM to serve this thing up, because each connection is an Apache process... so even though there's no database and only very simple PHP (to include headers, footers on the website), RAM is still going to get chewed up a lot...
Which brings me to:
- Should I be looking at another web server altogether?
- Should I just give up on the idea of an affordable solution, suck it up and let the browser companies host it?
Thanks in advance for any guidance!
[link] [7 comments]