You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a lot of prepared statements are cached, SHOW MYSQL STATUS (or any query against stats_mysql_global becomes slow because metadata related to all cached prepared statements are scanned in MySQL_STMT_Manager_v14::get_metrics() .
This doesn't simple make SHOW MYSQL STATUS slows, but also block traffic because of the held write lock.
The text was updated successfully, but these errors were encountered:
Prepared statements counters are now computed at runtime instead of on-demand.
Now MySQL_STMT_Manager_v14::get_metrics() doesn't depend anymore from the
number of prepared stataments cached.
The old code (slow code) is still present in the DEBUG version, and used to
validate the new counters. That also means that DEBUG versions are way slower
than non debug versions.
Prepared statements counters are now computed at runtime instead of on-demand.
Now MySQL_STMT_Manager_v14::get_metrics() doesn't depend anymore from the
number of prepared stataments cached.
The old code (slow code) is still present in the DEBUG version, and used to
validate the new counters. That also means that DEBUG versions are way slower
than non debug versions.
If a lot of prepared statements are cached,
SHOW MYSQL STATUS
(or any query againststats_mysql_global
becomes slow because metadata related to all cached prepared statements are scanned inMySQL_STMT_Manager_v14::get_metrics()
.This doesn't simple make
SHOW MYSQL STATUS
slows, but also block traffic because of the held write lock.The text was updated successfully, but these errors were encountered: