The article you referenced is more than 3 years old. I believe that starting with the V8 version introduced sometime around node 0.10.0, --max_old_space_size works great (we're using --max_old_space_size=8192 and, if I recall correctly, having no problems even when our process was using 4+gb of RAM).
On Thursday, June 4, 2015 at 2:02:21 PM UTC-7, Peter Rust wrote: > > *> what is the best way to determine what my memory footprint is* > > The *easiest* way is process.memoryUsage() > <https://nodejs.org/api/process.html#process_process_memoryusage>, the > *best* way depends on what exactly you want (there are some cool > analytics/memory profiling tools in the aforementioned links) > > *> how can I control it?* > > There is a command-line flag, --max_old_space_size > <https://github.com/joyent/node/wiki/FAQ#what-is-the-memory-limit-on-a-node-process>, > > but it only goes to a max of 1.4gb. If you need to go beyond that, this > article > <http://blog.caustik.com/2012/04/11/escape-the-1-4gb-v8-heap-limit-in-node-js/> > > discusses options. > > The article also mentions the "ulimit" command, which you may need if > you're on OSX and running up against the default maximum number of files > open simultaneously. > > > > > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/40aac503-4b2d-4aa8-9559-c64b3814596b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
