You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're currently evaluating the possibilities to auto-scale NodeJS applications and have found this module to be potentially suitable.
However the documentation (as well at the more complete article https://vexell.medium.com/autoscale-node-js-applications-with-pm2-and-pm2-autoscale-module-3129582dc72c) appears to mention the possibility to apply the auto-scaling settings (scale_cpu_threshold, release_cpu_threshold) only globally.
We'd like to be able to set these per-application so that different applications can use different settings. Is it (or will it be) possible?
There are some workarounds that come to our minds, however we'd really prefer the straightforward approach - just setting these parameters in the .config.js file or so.
The text was updated successfully, but these errors were encountered:
Hello @hostalp Thank you for you message. Yes, this is a good point. I guess the best place for that might be ecosystem config file. I will think how i can get access for that in the module (if it possible to use custom properties).
We're currently evaluating the possibilities to auto-scale NodeJS applications and have found this module to be potentially suitable.
However the documentation (as well at the more complete article https://vexell.medium.com/autoscale-node-js-applications-with-pm2-and-pm2-autoscale-module-3129582dc72c) appears to mention the possibility to apply the auto-scaling settings (scale_cpu_threshold, release_cpu_threshold) only globally.
We'd like to be able to set these per-application so that different applications can use different settings. Is it (or will it be) possible?
There are some workarounds that come to our minds, however we'd really prefer the straightforward approach - just setting these parameters in the .config.js file or so.
The text was updated successfully, but these errors were encountered: