solistics wrote:
brailsmt wrote:
150MB database is peanuts, I thought it was up around 1-2GB... If I wasn't "borrowing" wifi, I'd offer to host the DB myself on my machine, it has more than enough horsepower
Haha, the problem isn't the horsepower alone, it's the horsepower plus the bandwidth. I've got a beefy computer at home too, but even on Comcast's better days it wouldn't be able to host FLAK with reasonable latencies. To get even half a gig of RAM in a proper hosting facility is dang expensive. I took a look at those links you provided and a few others as well, and I don't think any of those options are going to be cheaper than even doubling the size of my current server.
Is it possible to cluster the DBs? I may be talking out my ass here, but if you could find 3 or more ppl to help host, that would split the bandwith and load. It'd add the additional cluster traffic between nodes, but with 3 ppl in the cluster, it'd save at least 1/2 the bandwidth...
If the problem is bandwidth, the RAM on the server won't be the limiting factor with a 150MB DB. I'm surprised comcast isn't already shaping traffic to your server to throttle the bandwidth. Comcast is a bunch of asshats with a local monopoly. I'm assuming you have a non-residential account, or they'd be shutting you down once they noticed the amount of traffic, since hosting a server is clearly against all residential contracts I've ever seen.
I'm good at throwing out ideas, feel free to keep shooting them down, maybe one will be golden...
Pardon the scattershot nature of this email...I blame the screwdrivers...