The approach that the module takes to process entities is a little naïve. It looks at every bundle with a field type that could contain an embed and enqueues every single entity in that bundle for later processing. On sites with large amounts of content this can take a very long time to build the queue, much less process it. We can do better by only enqueuing entities that actually have at least a reasonable chance of containing embeds.
When installing the module, only enqueue entities for which at least one of the relevant fields contains an `entity-embed` tag. The query needs to be run per bundle instead of just per content type, and I do hate running an unindexed `LIKE` query against a full text field, but unless you really do have embeds in the vast majority of your content the database hit is more than made up for by the reduced number of queue records that need to be created.
Patch attached.
N/A
N/A
N/A
Needs review
1.0
Code
The patch will have to be re-rolled with new suggestions/changes described in the comments in the issue.
Setting to "needs review" as a patch was provided.
Also related: 🐛 Query bundle key conditionally in install function Fixed
The posted patch didn't apply any more, I rebased the changes and incorporated the changes mentioned in #3 filing MR5