This repository has been archived by the owner on Oct 17, 2021. It is now read-only.
Fire-and-forget option for starting workers #111
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
...and the scheduler. Where a large number of workers needs to be started on a single host, it can be a long wait for each one to start before moving onto the next. This change offers a resque_fire_and_forget variable which will background the `nohup rake` command. This does of course have the disadvantage of ignoring any errors that might occur when executing rake, so this should only be enabled if the benefits outweigh that cost. It may also spike the load on the host as it tries to concurrently start as many processes as it can.
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.
...and the scheduler. Where a large number of workers needs to be
started on a single host, it can be a long wait for each one to start
before moving onto the next. This change offers a
resque_fire_and_forgetvariable which will background the
nohup rakecommand.This does of course have the disadvantage of ignoring any errors that
might occur when executing rake, so this should only be enabled if the
benefits outweigh that cost. It may also spike the load on the host as
it tries to concurrently start as many processes as it can.