> v8-profiler and node-profiler haven't been updated for newer versions of V8,
> I think. Have you tried node-webkit-agent?
> https://github.com/c4milo/node-webkit-agent

Thank you, node-webkit-agent works! \o/

Can somebody explain me the possibilities of a discrepancy in memory
use? According to 'top' my node server process needs 92mb of reserved
memory.

PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
27996 axel      20   0  639m  92m 6048 S   0.0  2.4   0:06.06 node

I also tested with a minimal "hello world" mini-webserver. With it
node needs 10mb RES on my system.

The heap in the profile reports 9mb of total use.
http://i.imgur.com/hZ7QP.png

What are the other 73mb? Any idea I can track that down?

On my computer it bein 2% sounds like nitpicking, but the VM i bought
the server runs on has 512MB so I don't want to explode it. Or rather
I'd like to know how much of the memory is "fixed" and how much is due
to the data i keep in memory of my processing. That is, I'd like to be
able to estimate how well it will (web)scale. I first thought the 92mb
were mostly due to my data, which would've ment it scales badly, but
if its only 100kb as I read the profile, it should scale well. Are the
70mb libraries through require? I tested to require them in the mini
server as well, but didn't change much. Maybe they just get collected
soon after.

Kind regards,
Axel

-- 
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

Reply via email to