Hi Bruno, thanks for the suggestions. yes we are using streamline fibers mode.
Several questions: 1) regarding the fiber mode memory oscillations that you saw: was this under node 0.10.x? and do you know if you had the same behavior under node 0.8.x? Also, the memory numbers you are quoting here are RSS usage, right? 2) do you know if streamline callbacks mode also avoids the memory oscillations? Thanks, Seth On Sep 19, 2013, at 12:46 PM, Bruno Jouhier <[email protected]> wrote: > Hi Seth, > > Are you using streamline in fibers mode for this test? If so it may be worth > upgrading to 0.11.x and trying generators mode. > > We had a high memory consumption in one of our processes. In fibers mode we > had very large oscillations on memory usage with high peaks and it was a bit > difficult to tell whether there was a memory leak or not. It looked more like > a fragmentation issue that was delaying release of memory because we were > getting sudden drops from 1,200MB to 300MB every 10 minutes. In generators > mode we got a lower memory usage, a very flat memory curve and no drift at > all (no memory leak :-). Memory usage kept oscillating between 210 MB and 240 > MB throughout the test. > > Bruno > > On Thursday, September 19, 2013 8:32:34 PM UTC+2, spollack wrote: > > > On Thursday, September 19, 2013 10:14:22 AM UTC-7, Ben Noordhuis wrote: > > Yes, that's correct. 1 GB is a bit on the low side these days, > especially when running on a virtualized machine where the physical > memory may be overcommitted. The easiest way to fix your issues is > probably to add more memory. > > Our app is running in Heroku, and the only dyno size options they provide > right now are 512MB or 1024MB. We could look at switching hosting providers, > but that is a bigger undertaking. So I'm definitely going to try to get node > 0.10.x to perform similar to 0.8.x for us if at all possible. > > > Maybe have a look at node-heapdump or node-webkit-agent. They're both > tools for creating and diffing heap snapshots. Finding out what is > using memory is a good first step. > > Thanks. I'll do some more experimentation with different --max_old_space_size > settings, and if that isn't working, i'll try looking at the heapdumps to see > what i can see. Do either of these tools give direct insight into non-heap > allocations? > > Thanks, > Seth > > > -- > -- > 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 > > --- > You received this message because you are subscribed to a topic in the Google > Groups "nodejs" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/nodejs/jD3fWckZgI8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
