Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.5, 10.6
Description
The variable innodb_thread_concurrency was useful years ago when computing resources were limited, but nowadays setting this value to anything than unlimited (0) makes little sense and actually makes things worse ,because queries have to wait outside InnoDB.
We have seen many customers mistakenly setting this to a small value like 16 or 64 and then complaining the server was slow.
In the latest instantation of the above problem I've seen (just today), the available slots were all taken by long running transactions (left open) and the server was stalled as a result.
So, a dangerous config option and IMHO a good candidate for deprecation/removal.
Thanks
Rick
Attachments
Issue Links
- blocks
-
MDEV-23397 Remove deprecated InnoDB options in 10.6
- Closed
- relates to
-
MDEV-23382 Change DB_ROLL_PTR format to allow more than 128 concurrent START TRANSACTION
- Open
-
MDEV-25883 Galera Cluster hangs while "DELETE FROM mysql.wsrep_cluster"
- Closed
-
MDEV-11382 AliSQL: [Feature] Issue#9: PROVIDE ADAPTIVE ALGORITHM FOR INNODB CONCURRENCY TICKETS
- Closed
-
MDEV-14462 Confusing error message: ib_logfiles are too small for innodb_thread_concurrency=0
- Closed
-
MDEV-23369 False sharing in page_hash_latch::read_lock_wait()
- Closed
-
MDEV-24759 Server hangs when innodb_thread_concurrency is reached and temporary sequences exist
- Closed
-
MDEV-31220 MariaDB:performance seems to be limited when the value of parameter innodb_thread_concurrency is not zero
- Closed