Best thing to try, add --nouse_idle_notification to the node command line, this disables the full garbage collects when node tells V8 it thinks its idle, but V8's garbage collection it does on every allocation should still take care of collecting garbage. Give that a try, watch the RSS in top or your favorite process monitor to make sure it's still garbage collecting (doesn't just leak), and hopefully the stalls will also go away. We found this totally eliminated the giant garbage collect stalls and did not noticeably impact process memory usage in our application.
On Thursday, August 2, 2012 11:48:15 PM UTC-7, sunjoy wrote: > > Hi guys, > > I am studying node.js. It is a wonderful utility to write network-based > application. > > Now, I have written a memcached server using node.js. You can have a look > at https://gist.github.com/3244607 > > I tested the program, and found it could reach 12000/s throughput. > However, during the test, I found sometimes the speed suddenly decreased > due to the GC pause from my mind. > > > Is there a way to improve my code ? > > > > Thanks > > Junyi > > > -- 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
