archive/node
1
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2025-08-15 05:38:47 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
Page: Frequently Asked Questions
Pages
API changes between v0.10 and v0.12 API changes between v0.10 and v4 API changes between v0.4 and v0.6 API changes between v0.6 and v0.8 API changes between v0.8 and v0.10 Breaking Changes Breaking changes between Node 7 and 8 Breaking changes between v4 LTS and v6 LTS Breaking changes between v4 and v5 Breaking changes between v5 and v6 Breaking changes between v6 LTS and v8 LTS Breaking changes between v6 and v7 CITGM Status CITGM known flakes CITGM results table Creating a CTC Meeting Issue ES6 Module Detection in Node Flaky tests Frequently Asked Questions Home Installing and Building Node.js Installing io.js via package manager Meetings: Creating a Hangouts On Air Event Merging pull requests with Jenkins Migrating IO polling from libev to libuv Migrating from v0.2 to v0.3 Migrating from v0.2 to v0.4 Statically linked executable Testing pull requests with Jenkins Windows Environment
1 Frequently Asked Questions
Brian White edited this page 2015-10-14 17:16:55 -04:00

  • Q: I'm experiencing reliability/memory spiking issues on a low-memory system, what's going on?

    A: By default, --max_old_space_size (which controls the upper limit of the V8 heap) is ~1.5GB. If your system has less memory than that, you will need to explicitly set this option to the appropriate amount of memory available to that process. For example, --max_old_space_size=128 will allow 128MB for that process.

Node.js community wiki

Node.js logo