-
-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to run multiple workers? #699
Comments
@adeeb1 GoodJob doesn't have a configurable way to run multiple processes (#150); the assumption is that there is a containerized environment that makes it easy to run multiple isolated processes. But assumptions are made to be challenged! Can you tell me:
|
Thanks for the quick reply @bensheldon!
Knowing what you said about containerization, I could easily just spin up more workers running good_job to get through these faster. For some reason I assumed the configuration would be the same, so it's good to have clarification on how good_job is expected to be deployed in production. I think I have my solution now: run more EC2 tasks for workers! |
Awesome! Happy to help! |
Before I switched to good_job, I used delayed_job, and I ran multiple workers in production with the command:
With good_job, I couldn't find a way to specify the number of workers. Would increasing the number of max threads be an equivalent? My jobs are being processed too slowly, and I need to allocate more resources to processing jobs from the queue.
The text was updated successfully, but these errors were encountered: