|
Top-level
@j12t It’s not a queue. But yes, if 1000 things are scheduled to run they will all run. It runs in the background though so doesn’t hold up requests, which is why it’s spawned at the end of other requests. Because web requests have a limited execution time it’s better to turn off the regular HTTP-invoked cron and run WP-cron from a system cron. Does that make sense? Too technical? Other questions? 3 comments
@j12t Sounds like you want an actual queue rather then job scheduling. Trouble is the only queuing solution I know runs off of wp-cron! https://github.com/deliciousbrains/wp-queue Do you know what cron event your sending is hooked onto? @j12t @ross how long does it take to run the process? For one single message, say. Is it a large number of traffic? Running on multiple servers? Things like this all fall into play depending on how you want to use it. I can probably help you out with understanding this if needed, email me some info about it: otto at wordpress.org |
Gregory's Server
@ross My use case is non-standard :-) For FediTest.org, I'd like to deliver outgoing ActivityPub messages asap, so my tests don't take longer than necessary. I've attempted to invoke wp-cron.php manually but it's not sending immediately ... 15 sec wait often works, but not always.