node -v
v0.8.0

cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04 LTS"

uname -a
Linux nowhere 2.6.39.1-x86_64-linode19 #1 SMP Tue Jun 21 10:04:20 EDT 2011 
x86_64 x86_64 x86_64 GNU/Linux

I am slightly surprised by the memory footprint of node.js in my setup.  
Here are my top memory hogs:

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  
COMMAND                                                                
 2359 mysql     20   0 1050m  41m 1536 S    0  9.8   1:31.64 
mysqld                                                                 
*16886 webmaste  20   0  919m  22m 7840 S    0  5.2   0:01.07 
node                                                                   
*15173 mongodb   20   0  623m  12m 1856 S    1  3.0   0:50.63 
mongod                                                                 
 2638 root      20   0  323m 8332 2232 S    0  1.9   1:38.38 
fail2ban-server                                                        
14583 root      20   0 73352 3420 2624 S    0  0.8   0:00.01 
sshd                                                                   
 2626 postfix   20   0 38120 3192 2212 S    0  0.7   0:00.17 
tlsmgr                                                                 
 2285 root      20   0 49948 2740 2156 S    0  0.6   0:00.30 
sshd                                                                   
16346 www-data  20   0 51656 2376  948 S    0  0.5   0:00.33 
lighttpd                                                               


I have three node.js express webapps served via vhost under a single 
node.js process which is itself behind a lighttpd proxy.  The only modules 
used by the three apps are connect, express, express-messages, jade, 
nodemailer and node-sqlite3.  That's it.  (The node apps are not using 
mongo or mysql.)  As you can see, the VM for node is approaching a 
gigabyte. Wow.  I might add that the web apps are just sitting there, not 
getting any hits.  For comparison, I see that the node REPL pulls 621MB of 
vm on this system.

I realize that the set size is a small fraction (about 24%) of the full 
image, and that only makes me worry more about how this setup will perform 
under load-induced memory pressure.

Is this to be expected with the node.js runtime, or do these results merit 
more digging by me?  

And if this is to be expected, does anyone have suggestions for sizing 
memory for a server which might host six to ten "simple, light-duty" 
webapps with sql backends?  As you may infer from above, this test was run 
on a small virtual machine with only 512 MB of RAM.  I would deploy on a 
bigger server.  How much bigger is a question.

Obviously, I am not Google or Twitter but I'd also like to be not stupid 
about this.

Thanks for reading.
Carlos

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