innodb_adaptive_max_sleep_delay
INFO
Rule IDs: cc_003
Overview
- Purpose
- Documented in the MySQL 8.4 manual as a server system variable (scope: Global). Purpose and semantics are described at the linked manual page.
- Dynamic (MySQL 8.4 reference)
- MySQL 8.4 marks this variable as dynamic (
Dynamic= Yes). Runtime changes useSET GLOBAL(global scope) orSET SESSION(session scope) — confirm syntax and persistence (SET PERSIST) in the manual. - Default value
- Default depends on MySQL version, build, and platform — see the manual page for this variable.
- Version and product notes
- MariaDB and Percona Server may use different names, defaults, or dynamic behavior; verify their documentation.
- Documentation
- https://dev.mysql.com/doc/refman/8.4/en/innodb-parameters.html#sysvar_innodb_adaptive_max_sleep_delay
- Other vendors
What is checked
Rules that reference this variable, with their severity and what each rule detects:
- INFO
cc_003: When innodb_thread_concurrency > 0 and high concurrency is expected, keep innodb_adaptive_max_sleep_delay enabled (non-zero). Disable only if < 16 typical threads.
Tuning guidance
- Recommended actions:
- When innodb_thread_concurrency > 0 and high concurrency is expected, keep innodb_adaptive_max_sleep_delay enabled (non-zero). Disable only if < 16 typical threads.
- Trade-offs: Thread concurrency controls balance CPU utilization against contention. Too many concurrent threads cause lock waits; too few leave CPU idle. Auto-management (concurrency=0) works well for most workloads.
Example
Consult the manual for whether SET GLOBAL, SET PERSIST, or SET SESSION applies.