This repository has been archived by the owner on Oct 16, 2019. It is now read-only.
Use resque-pool #161
Open
Use resque-pool #161
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
July 7, 2015 22:35
|
I defaulted to only using 2 resque workers, but if the memory usage isn't bad, you can probably fit at least 3 in there, and possibly more. Also, the installation docs should mention tweaking WORKER_CONCURRENCY before scaling up dynos. Or perhaps we should just tweak the default setting to a reasonable max and then scale up dynos when really necessary. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Only tested enough to see that it does spin up multiple worker processes.
Also adds
TERM_CHILD=1.