activejob-google_cloud_pubsub
activejob-google_cloud_pubsub copied to clipboard
No thread mode
for better scalability control, it's better if the worker run on single thread
--max-threads=N
cannot be used because the worker will consume all the messages, and reschedule then, running with --no-threads will block after each process, and not collecting the next message till ready to process it
That's what I was looking for!!! :shipit: