List:General Discussion« Previous MessageNext Message »
From:Van Date:July 15 1999 4:45pm
Subject:Re: Optimizing a P133 for MySQL
View as plain text  
> 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.
> --
> Ed Carp, N7EKG  	erc@stripped		940/367-2744 cell phone
> Owner: WeatherAlert/Digital Weatherman - NWS alerts via email/pager/Internet
>        DSOUTH-L backup, Terrorism, Shamanism, Hurricane mailing lists
> 		http://www.pobox.com/~erc
Ed,
Of course this is an option, as well.  The tip about not running more than
30-40 processes is very useful, though.  The specific issue about gateways
and bouncing specific tasks from one machine to another is somewhat
complicated due to the starkly different software environments running the
various businesses at this provider (IIS on NT vs. MySQL/Apache/PHP on
Linux),
so, I think our approach will be to see how the first two "stores" run on
the Linux box, and, if the activity is excessive, there's always the K6.2
400 w/ 128M DIMMS I can throw at the problem if need be.
Thanks a lot for yours and everyone's feedback.  This is an awesome group.
Best Regards,
Van

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