Problem/Motivation
Some sites report timeouts when regenerating tracking info, even when using the batched / limited version of the drush command.
This issue is to research the idea of using a queue to process items on sites with large amounts of content.
Obvious drawback is that until all items in the queue haven't finished processing, usage information on the site won't be accurate, so people should be aware and explicitly opt-in to this.
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork entity_usage-3215097
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
marcoscanoComment #6
marcoscanoBringing this in, will tag a new release so it's easier to make this available to others as well.
Thanks for contributing!