-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Configurable CONCURRENT_ACTIONS #850
Conversation
I approve of this idea! |
So, @Unitech is this PR something you will consider merging (after rebase) or should I close this and continue using our custom fork of PM2? |
Hi @kaaelhaa, this looks OK to me, could you handle the rebase ? Thanks, |
This could hurt some things of the PM2 core and remove rolling restarts, I don't recommend overriding this value |
a1ecd20
to
774cd65
Compare
"could"? |
Rebased. @Unitech From our usage and inspection of the code base I cannot see why this should hurt anything. It is a power user feature and should be treated as such by having a decent default value. If a user has set If you are uncertain about some use cases, please let me know so I can have them tested. |
@jshkurti Any thoughts on this? |
I'm going to refactor a bit reload/gracefulReload soon. |
I'm merging this because hey, why the heck not, if you're willing to take the risk, you should be able to do so and keep using the latests versions of PM2 :) |
Configurable CONCURRENT_ACTIONS
In our environment we have made the constant
CONCURRENT_ACTIONS
a configuration variable as this can significantly improve reload times when you have 8 processes of the same app.The default behaviour is, and should be, to only do one concurrent action. But for power users and environments where it make sense (e.g. can tolerate the overhead of extra processes running while old workers are finishing their jobs in gracefulReload-scenarios) this should be configurable.