heroku-node-settings
Advanced tools
Comparing version 1.0.2 to 1.1.0
{ | ||
"name": "heroku-node-settings", | ||
"version": "1.0.2", | ||
"description": "Prevent your Heroku Dyno from killing your Node app because of high memory consumption.", | ||
"version": "1.1.0", | ||
"description": "Helps you prevent your Heroku Dyno from killing your Node app because of high memory consumption.", | ||
"main": "index.js", | ||
@@ -6,0 +6,0 @@ "bin": { |
@@ -36,3 +36,2 @@ # Heroku Node Settings | ||
- `--max_old_space_size`: Sets the upper limit of memory node can use. The problem is that if your app reaches this value then Node will crash (memory allocation errors will start to show in the logs). | ||
- `--max_executable_size`: Max size of executable memory. It is smaller than the `max_old_space_size` so that your Node app will never reach the limit. | ||
@@ -50,1 +49,2 @@ Also note that, although these settings constrain the memory usage, there are other elements that can make the whole process use more memory that what these flags set (buffers, files, etc.). | ||
- http://erikcorry.blogspot.com.ar/2012/11/memory-management-flags-in-v8.html | ||
- http://fiznool.com/blog/2016/10/01/running-a-node-dot-js-app-in-a-low-memory-environment/ |
Sorry, the diff of this file is not supported yet
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
3998