High database load caused by SQL_CALC_FOUND_ROWS queries generated by TagDiv Com

Posted in: Newspaper
Post count: 2

Issue Description:
When activating and using TagDiv Composer together with the TagDiv Standard Pack in the Newspaper theme, the MySQL/MariaDB database quickly reaches maximum resource usage.

The problem comes from the large number of queries containing the SQL_CALC_FOUND_ROWS clause, which is highly inefficient on large tables such as wp_posts.
As a result, read operations become very slow and the database consumes excessive CPU and memory, eventually leading to site performance degradation and database connection errors.

https://www.zona-militar.com

Post count: 35449

Hi,
There would be some ways to reduce the number of queries, if you will consider them.
For one of the queries (sql_calc_found_rows):
Reduce the number of ajax usage on the website, as those are the ones that will make requests to load more posts.
So ajax features like ajax pagination – https://i.imgur.com/EfKi0za.pnghttps://i.imgur.com/sMeot5s.pnghttps://i.imgur.com/vrJq3BC.png
The ajax menus – https://i.imgur.com/n0K9hCN.png
Also the header live search makes requests when it is used – https://i.imgur.com/1ZvDwZx.png This can be deactivated when using a cloud header template. We added an option specially for it, as it can cause increased load on large websites.
The mega-menu pagination – https://i.imgur.com/T8kYzu4.png This can be deactivated when using cloud header templates, an option for this was also added for the same reasons mostly.
You can disable the ajax view count from here -> https://i.imgur.com/BIwbscU.png
Thank you!

Viewing 2 posts - 1 through 2 (of 2 total)
The forum ‘Newspaper’ is closed to new topics and replies.