Hi there,

We have recently upgraded from 4.7.12 to 4.7.20 and noticed a higher database load shortly (the next day) after the upgrade. There's no background tasks running so I'm not really sure what the source of this extra activity would be.

• PHP 8.1.30

• MariaDB 10.11.10 (10.5.27 when moving to 4.7.20, we upgraded to 10.11 a day later to see if it would help)

We have two database servers, one live and one archive. The high load was initially seen on the live server only, big CPU spikes rather than I/O. We upgraded MariaDB to see if it made any difference and while the big spikes have not returned on the live server I'm not convinced the MariaDB upgrade is the reason why, the archive server is now much busier than it was before too - just not to the extent that users notice.

Any idea what's going on? The long running queries in live were multiple instances of the below running for minutes at a time:

/*IPS\Conent\_Item::_comments:2129*/ SELECT forums_posts.*, author.*, author_pf... (truncated)

Archive server I'm not able to catch individual long running queries.

Thanks!

The first thing I would say there is that we advise on using mysql 8 rather than mariaDB. While MariaDB is said to be a drop in alternative to mySQL, it needs to be noted that we dont optimise for this. We optimise for mySQL, and have seen when people switch they get better performance.

Sure, but this had been working just fine on 4.7.12 for well over a year. The thing that changed was the Invision software.

If I search I can see other people have reported similar issues, somewhere between 4.7.13 and 4.7.16 is perhaps where there was an impacting change. Was this something already fixed by 4.7.20?

Yes, its very likely we have made changes to some sql statements that mariaDB did not like. As mentioned, we optimise for mysql