On Fri, Mar 30, 2012 at 10:51, Wan Li <[email protected]> wrote: > Hi everyone, > > My [email protected] web server runs in production for over one month without any > problem. Thank you, node. > > I noticed some strange things after long run. > ps ux | grep node > op 23356 0.0 0.0 659632 10268 pts/5 Sl+ Feb24 7:28 node app.js > op 23358 0.1 0.1 734888 17372 pts/5 Sl+ Feb24 63:19 > /usr/local/bin/node /home/op/app.js > op 23359 0.1 0.1 735968 19888 pts/5 Sl+ Feb24 75:44 > /usr/local/bin/node /home/op/app.js > op 23360 0.2 0.2 746444 36168 pts/5 Sl+ Feb24 142:45 > /usr/local/bin/node /home/op/app.js > op 23361 0.4 0.3 755628 49828 pts/5 Sl+ Feb24 235:56 > /usr/local/bin/node /home/op/app.js > op 23362 0.5 0.4 788496 70044 pts/5 Sl+ Feb24 282:09 > /usr/local/bin/node /home/op/app.js > op 23365 0.1 0.1 743856 26072 pts/5 Sl+ Feb24 100:12 > /usr/local/bin/node /home/op/app.js > op 23366 0.8 0.5 781292 88888 pts/5 Sl+ Feb24 412:00 > /usr/local/bin/node /home/op/app.js > op 23369 0.8 0.6 821580 103792 pts/5 Sl+ Feb24 409:08 > /usr/local/bin/node /home/op/app.js > op 23373 0.5 0.3 769264 53436 pts/5 Sl+ Feb24 279:46 > /usr/local/bin/node /home/op/app.js > op 23374 5.5 3.2 1253776 529216 pts/5 Rl+ Feb24 2801:30 > /usr/local/bin/node /home/op/app.js > op 23376 2.1 1.7 938984 282428 pts/5 Sl+ Feb24 1080:50 > /usr/local/bin/node /home/op/app.js > op 23377 3.8 2.3 1090680 374520 pts/5 Sl+ Feb24 1941:58 > /usr/local/bin/node /home/op/app.js > > 1. Some processes utilized far more CPU time than others, but I'd expect > they should be have similar load. No?
Load balancing is done by the operating system. The nodes in the cluster listen on a single socket, it's the OS that decides which node gets the connection. I've observed on Linux that if your cluster is mostly idle, the first few nodes receive the bulk of the work. > This application is built upon express, it proxy HTTP requests, serve a lot > of small files (sometimes we need to modify the content on-the-fly before > send). > 2. Some processes have high RSS. I searched around, but can't find a way to > take a snapshot or detect leaks. Do you have any suggestions? > Thank you! Try node-inspector (provided it compiles. It's kind of hit and miss). On a side note, I would recommend that you upgrade to v0.6.14. There have been a lot of bug fixes, including a few memory / resource leaks, since v0.6.6. -- 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
