Big problem to solve

[gwalters]

I have a customer running an accounting package that connects to a MySql data base on a server. 6 workstations connect to the server and run great. Fast and never a problem. However yesterday running the programs on the server directly got so slow that it takes 5 minutes to run a report that takes only 2 seconds on the 6 workstations. This is true for any program that accesses the data base. All other window functins work fine. This happened all of a sudden. Something is wrong with the server (all
computers are running XP pro) and I've no idea. Any suggestions would be appreciated.

[gwalters]

BTW running MySql 4.022 and ODBC 3.51

[Vikas Jayna]

Will have to monitor the mysql processlist using [b]show processlist[/b] to see what mysql is doing during those five minutes - is the connection established immediately? is the query executing or does the connection show the status as [b]sleep[/b]. Also, it would be worth seeing the performance of apache on the new machine - simply execute a script that does not use mysql and see how fast it executes.

[gwalters]

Thanks, I did this for a simple "next record" and got these results.

sleep    45
sleep    43
query    0  show processlist
sleep    2

I don't know the significance. The "next record" on the server using the customer inquiry program took about 10-14 seconds which would be instantly from all other workstations.

I also ran "mysqladmin -i 5 status" and could see no difference between the failing computer and one that
is working properly. Does this make any sense to you?

[fenway]

Sorry, are we talking about a MySQL program here? I'm confused.

[gwalters]

I have solved this problem!!!! Glory. Some bug somewhere enabled tracing on the ODBC data sources. I saw this comment on some forum. Getting rid of it solved the problem. I've no idea how it got set on.

Thanks all for taking the time to listen and respond

--------------------------------------------------------------------------------