List:General Discussion« Previous MessageNext Message »
From:Van Date:July 16 1999 4:46am
Subject:Re: Optimizing a P133 for MySQL {Interim Results}
View as plain text  
Okay, Folks, thanks and God bless to all who contributed to this post. 
I appreciate it more than you'll know.
I've installed and run the performance tests, and many of you were
correct.  A P133 with 48 Meg will not hold under the rigors of the
run-all-tests benchmark, to a degree on Linux in this hardware profile.
Truth is I received many ide timeout errors to the console when I woke
up this morning, but, stranger than truth, the tests completed and were
all successfull.  Yes the database attacks the machine very hard, but,
the kernel knows this and compensates with sufficient timeouts on the
2.2.9 kernel to deal with slow ide drives.

I'm not justifying using poor hardware for this project, but, I am
indicating that deficient hardware will not cry 'mama' when given a
load. 

I tested the production web server (apache) with 30 httpd processes and
it suffered a load of 0.00 across the board with 30 httpd processes
running when hitting it with 3 clients (all Linux running a while true
hit the server script using Lynx).

I'll update when I get the mod_auth_mysql built in and the mysql access
and referrer logs built into it over the weekend, but, the reality
appears to be that, although, it's pretty stupid to try this on a P133
with 48 Meg of RAM, it isn't fatal.  

Any comments, or criticism is obviously welcome.  >:)

Best regards, and thanks to all who joined this discussion.  It's truly
opened some useful eyes.

Van
-- 
=========================================================================
Linux rocks!!!   http://www.dedserius.com
=========================================================================
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