Hey everyone,

We recently updated our Invision Board from 3.4.7 to 5.0.3, and since then, we've noticed a significant increase in INP (Interaction to Next Paint) values in our Core Web Vitals.

The advertising setup and CMP are exactly the same as in the previous version, so the issue seems directly related to 5.0.3.

Has anyone experienced something similar? Do you know any tweaks, optimizations, or workarounds to improve CWV performance on the latest board?

Any insights would be greatly appreciated! Thanks in advance. 🚀

While he advertising etc is the same, you will have changed your infrastructure. The first thing I would advise on looking at would be your mysql performance. This would usually be the most common cause of performance related issues

 

While he advertising etc is the same, you will have changed your infrastructure. The first thing I would advise on looking at would be your mysql performance. This would usually be the most common cause of performance related issues

Hi Marc, thanks for the reply.
Considering that the forum has always been this size (10 million rows) and that the new server is 30% more powerful, the issue must necessarily be with board 5.0.3.

Simulating a normal user’s navigation, I found that with a mid-level CPU, the AJAX pagination takes 250ms to render the new page. I believe this is the main issue. Inside the advertising settings, I have enabled forced page reloads to avoid heavy AJAX loads for older browsers.

Moreover, the AJAX pagination adds the CSRF token to the URL, which might prevent proper cache optimization with a CDN. Maybe you could also try to speed up the AJAX loading in navigation for future releases (if possible).

I'll update you as soon as the INP values return to normal levels.

5.0 will be more intensive than version 3, as most other software is of that age. You are comparing software from around a decade and a half ago.

The size of the server and size of CPU is not actually the main factor. It would be the configuration of your mysql instance. That has to have changed, as they both support different versions of mysql.

 

5.0 will be more intensive than version 3, as most other software is of that age. You are comparing software from around a decade and a half ago.

The size of the server and size of CPU is not actually the main factor. It would be the configuration of your mysql instance. That has to have changed, as they both support different versions of mysql.

Thanks, Marc, for your response.
We have upgraded from PHP 5.6 to 8.1, which should already be more performant. The database has also been migrated from MySQL 5.6.x to MariaDB 10.6.20, which should further improve performance. The hardware has been upgraded primarily in terms of CPU (+300% – sorry, I previously missed a zero) and RAM (+100%).

Do you happen to have any best practices for MySQL configurations for a community with 400k+ topics and 10M+ posts?

We recommend running MySQL 8 over MariaDB variants. There are some slight improvements which we made to target MySQL 8 in the codebase.

With that said, we do not provide much in way of performance configurations as a software provider. Typically, your hosting provider or server administrator should be monitoring and making adjustments for your MySQL server as they see fit.

I just want to add in here that you could have the best computing power in the world but if you have not probably configured MySQL, PHP, etc... on your machine, it will not be able to fully utilize it. Which is why we recommend working with your hosting provider or server administrator to monitor and improve it.

 

Moreover, the AJAX pagination adds the CSRF token to the URL, which might prevent proper cache optimization with a CDN

I have opened a bug report to review this.