-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Set reasonable default for MAX_FORKS #5674
Set reasonable default for MAX_FORKS #5674
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a good idea to help people avoid shooting themselves in the foot.
awx/main/conf.py
Outdated
register( | ||
'MAX_FORKS', | ||
field_class=fields.IntegerField, | ||
allow_null=False, | ||
default=0, | ||
default=100, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe? Bumping it up to 200 sounds fine for those types of users - Though if we take 25 forks per 4GB as our baseline it'd be good to know if 200
would prevent a bad time for all the folks just running our recommended 4GB
minimum.
Based on our earlier chat, 100 was on the upper side of reasonable for a lot of scenarios. However, since this meant to be more of a sanity check I see your point that nudging this closer to 200 is probably the way to go. Some users might be doing alright with > 100 and so the additional warnings on upgrade wouldn't be welcome.
Build failed.
|
8613869
to
72f9609
Compare
72f9609
to
a6f063b
Compare
Build succeeded.
|
Build succeeded (gate pipeline).
|
SUMMARY
Set a reasonably sane default for
MAX_FORKS
.#5142