I met the same problem, add about 50m memory usage. I do not use socket.io.
Here is the 0.8.1 file node result:

 file /usr/local/bin/node
/usr/local/bin/node: ELF 64-bit LSB executable, x86-64, version 1 
(GNU/Linux), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, 
BuildID[sha1]=0x6a6a59a2e6d4ef768d609a795bd8e121a4996678, not stripped


On Wednesday, July 4, 2012 1:53:26 AM UTC+8, Ben Noordhuis wrote:
>
> On Tue, Jul 3, 2012 at 6:02 PM, chusi <chusi...@gmail.com> wrote: 
> > I updated nodejs on a ubuntu server (10.04.3 LTS) from v0.6.17 to 
> v0.8.1. 
> > The applications consists of a bunch of scripts that all connect 
> together 
> > over socket.io. I'm monitoring the memory usage i receive from 
> > process.memoryUsage().rss and graph it. I recognized that all my scripts 
> at 
> > least doubled in memory usage. Some that used to be around 16MB before, 
> > started using more then 30, and some climbed up to around 50MB, even if 
> they 
> > almost do nothing. 
> > 
> > I switched back to the old version and the memory stats got better 
> again. 
> > 
> > is anybody else seeing such a change in memory consumption as well? any 
> idea 
> > how to "resolve" this issue? 
>
> Sanity check - what do `file /path/to/old/node` and `file 
> /path/to/new/node` print? 
>

-- 
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Reply via email to