public inbox for [email protected]  

help / color / mirror / Atom feed

From: Mitch Pirtle <[email protected]>
To: [email protected]
Subject: Re: Server unreliability
Date: Wed, 29 Sep 2004 21:57:05 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

On Thu, 30 Sep 2004 01:16:26 -0000, Greg Sabino Mullane
<[email protected]> wrote:
> 
> > So far, I've had one person donate $10 ... in order to put a dedicated
> > server onto the network, I'd need alot more of those

Then perhaps a different approach needs to be taken?

> FWIW, I've been more than willing to put my money where my mouth is,
> but as long as we have banner ads all over out site, I'm not willing
> to provide money. I seem to recall that people offered to offset the
> costs of the banner ads earlier, but the discusion never got anywhere,
> mostly because nobody could produce the amount that the banner ads
> brought in.

I use Adblock for FireFox, and as a Gen Xer I don't see them anyway ;-)

> As far as suggestions, why not all chip in and get a nice dedicated server
> in a centralized place (e.g. Washington DC), get it up and running,
> and migrate things over one by one.

This was my thought initially, and servers themselves are actually
quite cheap (at ~$99 each) - that is why I asked about bandwidth
usage, as I believe this would be the cost factor.

For example, Server Beach (www.serverbeach.com) gives you a dedicated
machine for $99 monthly, and despite them being single processor
machines, we could have a dedicated webserver, dedicated database
server, and dedicated ftp/mail/whatever for ~$300...

I'm getting dual-xeons at aPlus.net for $200 or so, but I don't know
if PostgreSQL would need that kind of hardware if we could have
several servers.

Thoughts?  Discuss.  ;-)

view thread (74+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Server unreliability
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox