Master check and Tuning MySQL performance method (1/6)

I have been using the MySQL tutorial this database tutorial software, it works relatively stable, efficient and very high. In the face of serious performance problems, there are generally several possibilities:

1, the index is not well established;
2, the SQL writing is too complex;
3, configuration error;
4, the machine is really not load;

1, the index is not built well

If you see the CPU consumed by MySQL is very large, you can use the MySQL client tool to check.

Execute on Linux

/usr/local/mysql/bin/mysql-hlocalhost-uroot-p

Enter the password, and if there is no password, you can go to the client interface without the-p parameter.

Look at the current operation

Show Full Processlist

Can run a few more times

This command sees the currently executing SQL statement, which tells you the SQL, database name, execution status, client IP, account number used, elapsed time, and so on.

In my cache back end, this most of the time is not see the display of any SQL statements, I think this is more normal. If you see a lot of SQL statements, then this MySQL will certainly have a performance problem

Home 1 2 3 4 5 6 last