On Wed, Jul 4, 2012 at 11:39 AM, chusi <[email protected]> wrote: > On Tuesday, July 3, 2012 7:53:26 PM UTC+2, Ben Noordhuis wrote: >> Sanity check - what do `file /path/to/old/node` and `file >> /path/to/new/node` print? > > old 0.6.17: > ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked > (uses shared libs), for GNU/Linux 2.6.15, stripped > > new 0.8.1 > ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked > (uses shared libs), for GNU/Linux 2.6.15, stripped > > node is installed using chis-lea's package as described here: > https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager
Output from `file` looks good. If one binary was built for ia32 and the other for x64, you'd expect to see different memory profiles, but that's not the case here. I don't know if Chris lands patches on top in a way that changes memory consumption. Do you see the same behavior with a (tarball, git) source build? One thing to note is that V8 has a new and improved (but also more lazy) garbage collector. Run your app with --expose-gc and call gc() from time to time if memory pressure is a real issue - but I would generally advise against that. -- 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
