content_image/765220.jpg content_image/765223.jpg content_image/765226.jpg content_image/765229.jpg content_image/765231.jpg
<img src='content_image/765220.jpg'>

3 rows in set (0.00 sec) 

mysql> SHOW PROFILE; 

<img src='content_image/765223.jpg'>

7 rows in set (0.00 sec) 

mysql> SHOW PROFILE FOR QUERY 1; 

<img src='content_image/765226.jpg'>

4 rows in set (0.00 sec) 

mysql> SHOW PROFILE CPU FOR QUERY 2; 

<img src='content_image/765229.jpg'>

7 rows in set (0.00 sec) 

<img src='content_image/765231.jpg'>

## Note 

Profiling is only partially functional on some architectures. For values that depend on the getrusage()  system call, NULL  is returned on systems such as Windows that do not support the call. In addition, profiling is per process and not per thread. This means that activity on threads within the server other than your own may affect the timing information that you see. 

Profiling information is also available from the INFORMATION_SCHEMA PROFILING  table. See Section 26.3.24, “The INFORMATION_SCHEMA PROFILING Table” . For example, the following queries are equivalent: 

## 13.7.7.31 SHOW PROFILES Statement 

SHOW PROFILE FOR QUERY 2; SELECT STATE, FORMAT(DURATION, 6) AS DURATION FROM INFORMATION_SCHEMA.PROFILING WHERE QUERY_ID = 2 ORDER BY SEQ; 

