Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

heroku-node-settings

Package Overview
Dependencies
Maintainers
1
Versions
4
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

heroku-node-settings - npm Package Compare versions

Comparing version 1.0.2 to 1.1.0

4

package.json
{
"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

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc