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