Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
10.3.37, 10.4.27, 10.5.18, 10.6.11, 10.7.7, 10.8.6, 10.9.4, 10.10.2
-
CentOS 7
Description
After upgrading part of our systems to 10.6.11 the MariaDB server uses much more CPU compared to 10.6.10.
We were upgrading to 10.6.11 for the fix to MDEV-29843, but started to roll back due to load issues with that version.
Server config is the same as on MDEV-29843;
~8 MariaDB instances per server, issue is worse on systems with a higher number of queries, where it's using 100% cpu, with notocable repsonsiveness of the system
Attachments
Issue Links
- is blocked by
-
MCOL-5361 prepare/execute : accomodate latest changes in server 10.6.11
- Closed
- is caused by
-
MDEV-16128 Server crash in Item_func::print_op on 2nd execution of PS
- Closed
- is duplicated by
-
MDEV-30096 Memory leak 10.3.37 and 10.6.11
- Closed
-
MDEV-30114 prepared statements spend a lot of time in cleanup
- Closed
-
MDEV-30116 Executing prepared statements may get slower over time
- Closed
-
MDEV-30274 Massive trigger performance drop after update
- Closed
- relates to
-
MDEV-30848 Memory leak in MariaDB 10.6
- Closed
-
MDEV-30889 Memory leak issues with MariaDB 10.6.12 and OOM Crashes
- Confirmed
-
MDEV-30355 set names effects performance significantly when compiling function
- Closed