Yoast indexable is hitting performance

@dnikola,

We’re very sorry. For sites with more than 10,000 posts, we advise using the [WP CLI command to do the indexation on the server](https://yoa.st/wp-cli-index).

Thank you.

Perhaps the plugin should be re-written so that the conversion can be done in smaller batches every so often triggered by wp-cron. Of course the plugin would then need to detect when a page is using the new method yet or still the old method during this transition period.

This would serve to keep the load down and allow for site with a large number of posts to eventually get them all processed without resorting to wp-cli although that still’s likely the best option for advanced users.

I myself don’t know the extent of things yet, because I haven’t updated any of my sites to 14 yet because I know better than to trust first releases of new features with the Yoast plugin because they often never work right.

Hello @suascat_wp

and how can wp cli help when again need to query db ?

Also what is a point of this inexables? I mean I have choose to not process with index (option to hide notice and continue as before)

I see now a db table wp_yoast_indexable is filling, and for around 200K posti is 250MB

so it will grow on 800mb when finish thus indexing and I will get what?

Hi @endymion00 , @dnikola

If you don’t want to run the whole indexing at once either through the UI or WP-CLI, the plugin will also do a “lazy” indexing of the posts that get traffic. This means that when a post receives traffic, the plugin will index the data for that post automatically without you having to actually run the whole process.

You can find more information about why we made these changes and the performance benefits we expect from them here: https://developer.yoast.com/blog/the-exciting-new-technology-that-is-indexables/

Closed due to inactivity