DB CPU Usage – Indexables

Hi @matanzari,

Thank you for creating a separate topic. We apologize for having these issues.

The new way that Yoast SEO 14.0 and up works is that we save the metadata in a separate database table and for existing data, we move it to the new table as well. This indeed might have some impact on performance or resources in the first period of using it. You can find more info on this change here: https://yoast.com/yoast-seo-14-0/.

To get back to the issue here. We would like to know more. Did you manually click the ‘Speed up my site’ button after the update? If you did, we encourage you not to do this on very large sites. This might sound counter-intuitive, but hear us out.

Yoast SEO will “lazy load” the new indexables feature as you, your authors, and your visitors read, write, and update content. In a few weeks, try running the site-wide scan again. If it still times out, you can continue to lazy load the content on your site until the process is low enough for your server resources or ask your server admin or web host to temporarily increase the timeout length while the process completes. Once it’s done, you should not need to do it again.

Hey,

The issue came up right after the update, without manually clicking ‘speed up my site’.

From what we see the cause of the issue is the shutdown hook which transfers 25 objects (posts, terms, etc) to the new tables.
Database stats shows that the high load comes from write operations, which I guess are the writes to the new table.

Using the cli is also an option (I see that this is supported), but before doing so I need to know how long this is going to take. The best option for me here is as follows:

• update Yoast
• disable indexables lazy load completely
• run the process via cli when traffic is low (maybe at night)
• enable indexables lazy load (I guess this is not needed)

Is that possible? I see that there is a filter for the amount of items to transfer on shutdown – what happens if I set this to 0?

Thanks,
Matan.

Hi Matan,

The lazy load should only run for pages that haven’t been indexed already. From what we understand from your question, it would not be necessary to disable the lazy load if you’re going to run the process using WP-CLI.

Unfortunately, we’re not able to estimate how long the process to re-index the SEO data will take for your site. If this is a concern, it may be best to test the update and indexing by creating a copy of your site or a staging site.

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.