MySQL Bugs: #113469: Affected by Bug 104576 partition table access second index lead to cpu high load

Bug #113469	Affected by Bug 104576 partition table access second index lead to cpu high load
Submitted:	20 Dec 2023 6:54	Modified:	20 Dec 2023 15:44
Reporter:	Nilay Shah	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S5 (Performance)
Version:	8.0	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
we went live with partitioning on 7 tables which already had heavy count and size of data .Now we have seen that since partitioning got live the CPU is hitting 100% and we have many secondary indexes on each tables too.Also since partitioning column needs to be part of unique indexes heance have been part of primary keys too.

How to repeat:
have a similar structure introduced and have about 100 million records with multiple json .this table is hit many a times in a minute.

we ae already on MYSQL 8.0.32 on AWS RDS

Hi Mr. Shah,

Thank you for your bug report.

However, we cannot repeat the behaviour that you are describing.

We need a full test case, with all tables and all their rows and the operations that you are running.

However, this is not a bug at all. It is a very well known fact that tables with many partitions have a high load on the server hardware.  This can be mended, to certain degree with configuration tuning.

You have to tune very carefully your hardware, OS and MySQL RDBMS to decrease CPU utilisation.

You should be also running on the very powerful computer with many CPU cores and very large memory.

So, even if we had the entire test case, we would have run it, all alone, on the very powerful server, which means that we would not be able to repeat it.

Can't repeat.

Mysql is on aws rds so OS tuning is not under purview