Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
To enable better control of the InnoDB purge subsystem, it would be good if the maximum number of purge tasks were settable by the user while the server is running:
SET GLOBAL innodb_purge_threads=1; |
# run a heavy workload
|
# let the history be discarded faster while the server is less busy |
SET GLOBAL innodb_purge_threads=32; |
Independently of this, MDEV-16260 or MDEV-26356 may improve the way how the purge threads are scheduled. This task would only make the maximum number of concurrent purge tasks configurable.
Attachments
Issue Links
- is duplicated by
-
MDEV-11024 Make number of purge threads variable dynamic
-
- Closed
-
- relates to
-
MDEV-16260 Scale the purge effort according to the workload
-
- Open
-
-
MDEV-26356 Performance regression after dict_sys.mutex removal
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Link | This issue relates to MENT-599 [ MENT-599 ] |
Link | This issue relates to MDEV-16260 [ MDEV-16260 ] |
Link |
This issue relates to |
Assignee | Vladislav Vaintroub [ wlad ] | Matthias Leich [ mleich ] |
Attachment | MDEV-26520.test [ 58966 ] |
Assignee | Matthias Leich [ mleich ] | Vladislav Vaintroub [ wlad ] |
Attachment | output.txt [ 58971 ] |
Assignee | Vladislav Vaintroub [ wlad ] | Matthias Leich [ mleich ] |
Assignee | Matthias Leich [ mleich ] | Vladislav Vaintroub [ wlad ] |
Fix Version/s | 10.7.1 [ 26120 ] | |
Fix Version/s | 10.7 [ 24805 ] | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 124755 ] | MariaDB v4 [ 134465 ] |
Link |
This issue is duplicated by |