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
Is your feature request related to a problem? Please describe:
Currently, statements_summary_history use LRU cache strategy to cache recent 200 statements and each statement with 24 histories by default.
The problem is, the history statements can be evicted by the new statement, so the variable tidb_stmt_summary_history_size (which default value is 24) doesn't mean STATEMENTS_SUMMARY_HISTORY can alway provide the last 24 statements history.
I hope we can find another cache strategy for statements_summary and also don't have to pay too much memory.
Feature Request
Is your feature request related to a problem? Please describe:
Currently,
statements_summary_history
use LRU cache strategy to cache recent 200 statements and each statement with 24 histories by default.The problem is, the history statements can be evicted by the new statement, so the variable
tidb_stmt_summary_history_size
(which default value is 24) doesn't meanSTATEMENTS_SUMMARY_HISTORY
can alway provide the last24
statements history.I hope we can find another cache strategy for statements_summary and also don't have to pay too much memory.
Describe the feature you'd like:
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
The text was updated successfully, but these errors were encountered: