`innodb_concurrency_tickets`

INFO

Rule IDs: cc_004

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 use SET GLOBAL (global scope) or SET 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_concurrency_tickets
Other vendors: MariaDB KB Percona Docs

What is checked

Rules that reference this variable, with their severity and what each rule detects:

INFO cc_004: Adjust innodb_concurrency_tickets based on workload: lower for fairness to small queries, higher to let large queries complete without re-queuing.

Tuning guidance

Recommended actions:
- Adjust innodb_concurrency_tickets based on workload: lower for fairness to small queries, higher to let large queries complete without re-queuing.
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.

Generated from the MySQL Advisor documentation build. Dynamic Yes/No reflects the excerpt aligned with Oracle MySQL 8.4 reference material consumed by this project.