> we have some very long running apps we are trying to reduce the footprint on and unloading certain modules seems to be a good start
To be honest, that doesn't sound like a very good start. If your long applications have a growing footprint then you are leaking memory somewhere. "Cleaning up" modules you're not using anymore will save you maybe 10mb flat. On Mon, Sep 3, 2012 at 3:49 PM, Ben Noordhuis <[email protected]> wrote: > On Mon, Sep 3, 2012 at 9:02 PM, Bradley Meck <[email protected]> > wrote: > > How do people unload entire modules after they are done using them, we > have > > some very long running apps we are trying to reduce the footprint on and > > unloading certain modules seems to be a good start. For example if we > could > > eventually end up with something like: > > > > require.unload('nconf') after the configuration phase of startup. > > delete require.cache['nconf']? > > -- > 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 > -- 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
