On 17/09/2012, at 16:14, Ryan Schmidt wrote: > On Sep 17, 2012, at 09:03, Ben Noordhuis wrote: >> On Mon, Sep 17, 2012 at 3:40 PM, Ryan Schmidt wrote: >>> So do I understand correctly: a node program could use up all the >>> computer's memory? >>> >>> If I then need to launch additional programs, will node notice this and >>> reduce its memory usage so that the new program doesn't incur virtual >>> memory penalties? >>> >>> Is there a memory size at which this becomes a performance problem—for >>> example what if I run a node app on a server with 128GB of RAM? >> >> If you manage to fill up 128 GB, you get a cookie. The 2 GB that was >> reported earlier in this thread is close to the maximum that V8 will >> allocate. >> >> If that's still too much, you can limit the heap size with >> --max-old-space-size=<x> where <x> is in megabytes. > > I like cookies. But let's change the example. Suppose I have a server with > 2GB free RAM and I launch a node app. Over time it will occupy all 2GB of > free RAM as a consequence of the garbage collection system, even though it's > not really using the memory. Now I need to launch another program that needs > 1GB of RAM. What will happen?
Nothing. No problem. You even can have 10 programs with 1 terabyte mapped to each and all will be good... until the programs start to *really* use that memory, then, the OS *may* need to start swapping pages to/from disk like crazy, or not, it depends: if the combined *real* usage is > phisical RAM it will swap, if it isn't, it won't. -- Jorge. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: 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 post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
