List:General Discussion« Previous MessageNext Message »
From:Chris Trown Date:July 15 1999 5:36pm
Subject:Re: Optimizing a P133 for MySQL
View as plain text  
On Fri, Jul 16, 1999 at 12:27:48AM +0800, Orlando Andico scribbled:
> On Thu, 15 Jul 1999, Ed Carp wrote:
> ..
> > Perhaps a more rational solution would be to have a "gateway" machine that
> > keeps track of the number of httpd processes on each machine, then
> > redirects the incoming connection request to an appropriate machine,
> > instead of trying to run a bazillion processes on one machine.  Hardware
> > is cheap, especially older P166/P133/486dx4-100 hardware, and you could
> > probably afford to put up several P133's for the price of a P300.
> 
> That's definitely not as easy as it sounds. Cisco sells such a product -
> it's called Local Director and costs.. a large sum of money ($25K-ish).
> That should give you an idea how "easy" it is to pull off a stunt like
> that.
> 

     One could get an 8-port Foundery Networks ServerIron for about $5k.  It 
can load balance, with the added bonus of being usable for transparent web 
caching.

Chris...

-- 
What's the point?

An NT server can be run by an idiot, and usually is.
PGP fingerprint: 063FCE320681C336  78C164FC9B2F91EA
Thread
DISTINCT keyword not doing as I expect...DC Mahoney15 Jul
  • Re: DISTINCT keyword not doing as I expect...Paul DuBois15 Jul
    • Re: DISTINCT keyword not doing as I expect...jkraai15 Jul
  • Optimizing a P133 for MySQLVan15 Jul
    • Re: Optimizing a P133 for MySQLSasha Pachev15 Jul
    • Re: Optimizing a P133 for MySQLJunster15 Jul
      • Re: Optimizing a P133 for MySQLOrlando Andico15 Jul
        • Re: Optimizing a P133 for MySQLJunster15 Jul
          • Re: Optimizing a P133 for MySQLOrlando Andico15 Jul
            • Re: Optimizing a P133 for MySQLEd Carp15 Jul
              • Re: Optimizing a P133 for MySQLOrlando Andico15 Jul
                • Re: Optimizing a P133 for MySQLJon Drukman15 Jul
                  • Re: Optimizing a P133 for MySQLOrlando Andico15 Jul
                • Re: Optimizing a P133 for MySQLChris Trown15 Jul
                  • Re: Optimizing a P133 for MySQLEd Carp15 Jul
                    • Re: Optimizing a P133 for MySQLOrlando Andico16 Jul
                      • Re: Optimizing a P133 for MySQLVan16 Jul
              • Re: Optimizing a P133 for MySQLVan15 Jul
              • Re: Optimizing a P133 for MySQLT├Ánu Samuel16 Jul
                • Re: Optimizing a P133 for MySQLJon Drukman16 Jul
        • Re: Optimizing a P133 for MySQLJon Drukman15 Jul
      • Searching across multiple tablesBrighten Godfrey15 Jul
        • Searching across multiple tablessinisa15 Jul
        • Re: Searching across multiple tablesChristian Mack21 Jul
    • Re: Optimizing a P133 for MySQL {Interim Results}Van16 Jul
      • Re: Optimizing a P133 for MySQL {Interim Results}Ed Carp16 Jul
  • DISTINCT keyword not doing as I expect...Michael Widenius30 Jul
Re: Optimizing a P133 for MySQLDerick H Siddoway16 Jul
Re: Optimizing a P133 for MySQLKen Farwell16 Jul