The existing Drush commands in the entity_mesh module use drush_batch for processing items. On large sites with many entities to process, this can lead to memory leaks, causing the command to fail and not all items to be processed.
Because the process is handled in a batch, it's not possible to resume the operation from where it left off. If the process fails, the entire task must be restarted from the beginning.
This issue is a feature request, so there are no specific steps to reproduce a bug. The problem is related to the performance of existing Drush commands on large-scale sites.
The entity_mesh module already contains a Queue Worker at src/Plugin/QueueWorker/EntityMeshQueueWorker.php which is a more robust solution for processing large numbers of items asynchronously.
The proposed solution is to:
This approach will:
Create the new Drush command that enqueues the items. This will involve writing code to query the relevant entities and add them to the queue for processing by the existing `EntityMeshQueueWorker`.
Active
1.0
Code
There is a problem with the memory, we tried to reset the node cache, but it still increments with each item, so we should review how to solve it.