Atle Veka wrote:
Replicating a live setup, especially one running on the web is extremely
difficult if not near impossible. Assuming you don't have the freedom to
stop/start your mysqld for tuning/tweaking, here are some things you can
do:
- Enable slow-query-log
- Enable query log
- Query processlist periodically and save results where queries have been
processing for X amount of time
With this information you can profile your queries and use 'EXPLAIN
<query>' to optimize where needed, aka adding indexes, etc.
I simply haven't found it worth it to replicate live setups in order to
look for bottlenecks. It's much easier and less time consuming to do
things like above and generally being in tune with your system. Setting up
performance graphs based on your system or mysqld performance is worth the
time.
Atle
-
Flying Crocodile Inc, Unix Systems Administrator
Hi, Atle -
This is pretty much what I've been doing here. I am running queries
which appear to be "slow" from the live machine to the testing machine.
Although mundane, it gives me a pretty good idea of what I'm up against.
I think, however, I'll see a major speed improvement when moving from
MySQL 3.23.58 to 5.0.22, no? :) This current server is a bit dated,
which is the reason why I'm about to rip it apart.
I'll also go ahead and plug your service here, as I'm sure you won't
mind. I've used one of your sister companies in the past, and it has
helped me out a lot.
Thanks
-dant
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
