Comments on: Profiling MySQL queries from Performance Schema

It's a shame SET profiling = 1; is deprecated > 5.5. I just activated performance_schema and a query that took 0.51 seconds, now takes 2.32 seconds. There may be other reasons (hence why I am opt...

https://www.percona.com/blog/profiling-mysql-queries-from-performance-schema/#comment-10967394

You'll have to enable the proper consumers and instruments. What Jervin said in the comment above is correct but the consumers query does have a typo. The fixed query is: UPDATE performance_schem...

https://www.percona.com/blog/profiling-mysql-queries-from-performance-schema/#comment-10965847

Jervin, I could not get any from events_statements_history_long even after enabled setup_instruments and setup_consumers version 5.6.24 (Percona)

https://www.percona.com/blog/profiling-mysql-queries-from-performance-schema/#comment-10854869

Vlad, Have you enabled your consumers and instruments for statements and stages?

 UPDATE performance_schema.setup_instruments SET
ENABLED = 'YES', TIMED = 'YES' WHERE NAME LIKE 'statement/%'...

https://www.percona.com/blog/profiling-mysql-queries-from-performance-schema/#comment-10740320

I could not repeat this with mysql 5.6.11. mysql> SHOW VARIABLES LIKE 'performance_schema'; +--------------------+-------+ | Variable_name | Value | +--------------------+-------+ | performance_s...

https://www.percona.com/blog/profiling-mysql-queries-from-performance-schema/#comment-10740293