Your version has some big issues, try upgrading it, also, using the
variables to setup memory, index, sort and buffer use would be good, I
don't know exact values for your needs, but the MySQL Manual has some
tips on this, and also describes each variable use.
Jorge's suggestion is a good one, if your server don't need to resolve
the database server's name, you'll reduce time needed (assuming you
have the web server and mysql running at the same machine).
Check logs for hanging clients, it was a major issue before I upgrade
to 4.1.11. 4.1.7 was slow on queries with sort and subqueries, and
even was hanging every time a subquerie had an ORDER BY and LIMIT
clause. Try logging warnings (for a while, it takes memory and
resources too) and check for connections killed due to hanging, reduce
the wait_timeout and interactive_timeout (whatever you use) to check
Check your tables frequently (when there are less users on it) for
errors and optimize it. NTFS and FAT fses are likely to corrupt files
on high demands systems (IMHO), so, a chkdsk often is good (but that
demands a reboot).
Are you indexing your tables? Optimize index use and query_cache and
you'll get better performance, also, full text searches were killing
our server, it MUST be reduced, the LIKE clause is good, but it takes
resources as hell.
Any suggestion that would give you more information on demand will
slow your server (logging, checking clients, checking tables), so, be
careful, its a production system and customers hate when you say:
"Sorry, its slow because I'm trying to make it faster". *lol*
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------