web-push-php VS action-scheduler

However, the above code is slow and there was a problem with how the batchSize parameter from the web-push-lib worked during my initial tests. This parameter defines the batches size during flushing, by making asynchronous HTTP requests. You can see those batches as concurrent requests, and they can potentially create high spikes in memory and CPU usage, which can cause some weird errors in the downstream components like:

I’m actually working on a plugin that does exactly this. I use a library called action scheduler to split the import into one “action” per post and then use this library to process those actions in the background using “asynchronous actions” for creating and updating posts. This makes it so that you don’t run into issues with timeouts or import process hogging massive amount of server resources.

- action scheduler(queued background processing) , which still uses wp-cron but can be replaced with a custom implementation

2) For something this large, that will happen on a recurring basis, look into WP Action Scheduler. It's developed / maintained by Automattic currently, and is used in such large-scale plugins as WooCommerce: https://actionscheduler.org/

I would use ActionScheduler. It's designed almost exactly for something like this: https://actionscheduler.org/

Action Scheduler is a library bundled with many other plugins, including WooCommerce. It's used for, as the name suggests, queuing actions. https://actionscheduler.org/

There are sophisticated ways for background processing in WordPress like Action Scheduler used in Woocommerce, which has automatic adjustments like: