Feature proposal #5805
closed
Implement batching for internal users usage
Description
Currently the internal users usage loads every user and passes them through the action. Implement batching so it can be done over a period of time instead of all at once as it's causing memory limit issues.
Updated by krileon about 7 years ago
Easiest way to do this is parse a number of users then redirect back to the internal users trigger with the next batch specified.
Updated by krileon about 7 years ago
Redirects won't work due to too many redirects. Likely will have to be ajax requests.
Updated by krileon about 7 years ago
- Target version changed from 7.0.0 to 7.1.0
Needs to be done with internal paging so subsequent requests will carry on to the next batch.
Updated by krileon almost 7 years ago
- Target version changed from 7.1.0 to 10.0.0
Updated by krileon almost 6 years ago
- Target version changed from 10.0.0 to 8.0.0
Updated by krileon almost 6 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Implemented basic batching with 2 new parameters. 1 for supplying the batch limit (number of users per request) and the other for the current batch to process. The current batch parameter will update as the batches are processed, but for management purposes can be zeroed or changed as needed encase a batch needs to be reran.
No additional database storage was needed; this is all just kept a part of the plugins params. There are no redirects or additional HTTP requests. It simply runs a single batch per call. The next call will run the next batch. So your CRON should be appropriately setup to run the necessary number of times to process the entire queue.
This is default disabled (batch limit of 0) to avoid breaking existing usages.