[MDEV-11153] Introduce status variables for table cache monitoring and tuning Created: 2016-10-26  Updated: 2017-10-31  Resolved: 2017-10-31

Status: Closed
Project: MariaDB Server
Component/s: Locking
Fix Version/s: 10.3.3

Type: Task Priority: Minor
Reporter: Elena Stepanova Assignee: Sergey Vojtovich
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-10296 Multi-instance table cache Closed
Sprint: 10.3.3-1

 Description   

1. Since MariaDB's definition and use of table_open_cache_instances is different from MySQL's, it naturally calls for a status variable which would indicate how many instances are in use at the moment. MySQL does not have it, but it's not needed there, because there table_open_cache_instances shows exactly that.

2. MySQL 5.6/5.7 has status variables Table_open_cache_hits, Table_open_cache_misses, Table_open_cache_overflows. Even though MariaDB's table cache tuning is more automated than MySQL's, the variables can still be useful in MariaDB too.



 Comments   
Comment by Sergey Vojtovich [ 2017-08-10 ]

serg, please review patch for this task.

Generated at Thu Feb 08 07:47:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.