After update 10.0.0 degraded MySQL performance. Anyone also have this problem?

AdamM

Hi
This is a purely discussion thread not intended to insinuate that it is the fault of the new 10.0.0 release
I just want to find the cause of this problem.

Have any of you also noticed reduced performance in MySQL after the new release of Enhance and updating MySQL to 8.0.35?

I use simple test with plugin - https://wordpress.org/plugins/wpperformancetester/

On my small server with Intel, I noticed a drop in performance with the same my.conf settings.

Now:
Total Time (seconds) - above 10
Queries Per Second - max 1800

Before update:
Total Time (seconds) - below 8
Queries Per Second - max 2600

To me, this is a very big drop in performance....
This is just strange.... also earlier on regular settings in Enhance when I changed innodb_flush_log_at_trx_commit to 0 the performance was the highest, now there is no difference.

Can anyone also check this as well? Maybe someone has more information? Does MySQL version 8.0.35 have any performance degradation?

Regards

JohnB

AdamM You've probably checked this already but did you verify your my.conf settings are actually applying, to rule out the enhance update breaking that somehow and reverting mysql to default configs?

twest

You can see the changelogs for versions between x.x.28 to x.x.35 here (minor version updates in the table of contents):
https://dev.mysql.com/doc/relnotes/mysql/8.0/en/

I couldn't find any changes to flush log commit config. Lots and lots of bug fixes and quite a few performance improvements tho.

Has the average load or ram consumption changed any? Has average disk io changed any?

AdamM

twest
Yes, I also checked the changelog and didn't see anything about performance degradation. I didn't change anything. Only the Enhance update has been performed. This is not my first experience with database optimization, so I'm surprised...

DracoBlue

I switched to MariaDB and the performance is better than MySQL.

AdamM

Didn't anyone pay attention to it?

josedieguez

sadly no, we were waiting for mariadb, so never tested/benchmarked mysql.

twest

Well this is concerning...

I decided to give that plugin a tester and also try resaving my.conf and restart the DB container so I could test a before/after scan to see if it changes anything to help add some data to this post.

Well... I can't restart any of my DB containers. Getting error:
database role failed to restart. cannot read properties of undefined (reading 'id')

That's not good 😩

Adam

twest database role failed to restart. cannot read properties of undefined (reading 'id')

That's a UI bug, it's fixed in 10.1.0 which will be released imminently. If you edit my.cnf through the UI you will be prompted to restart mysql at this point (which works fine). If you are editing it from the server itself, run docker restart mysql to restart the service.

twest

Well, I didn't figure out that issue with restarting database container, I will wait to hear if other users have the same problem before submitting support ticket so we can see if it's a widespread issue.

As for the test. I did a hard reboot on a server (so I could test my.conf loaded), and reran that test plugin. No significant change in scores. I'm doing this all from my phone, I will investigate that my MySQL config didn't get borked from the update more thoroughly tomorrow when I am at my desk.

Would really appreciate anyone else able to test restarting their DB container to see if it's widespread 🙂