On Tue, Sep 24, 2013 at 5:47 PM, Konstantin Root <[email protected]> wrote: > We are using 64-bit Node.js 0.10.18 and it seems that its not possible to > use more than ~3GB memory inside one application. > Application is run with "--max_old_space_size=8192" flag on server with 8GB > ram, but after consuming ~3GB memory application crashes with message below > - there is still 3GB free left on the server when this happens: > "[27349] 348673 ms: Scavenge 3137.5 (3202.3) -> 3128.4 (3206.3) MB, 17 ms > [allocation failure]. > FATAL ERROR: CodeRange::GetNextAllocationBlock Allocation failed - process > out of memory" > Problem is easily reproducible in our service. > > Any idea how to solve this problem? Any other flags to control memory pool > for Node.js/V8? > One of our services grew very quickly from initial idea and now we process > 20+mln records in memory to do periodic realtime analysis. > I really hope that there is solution for this - another option would be to > rewrite this part in Go/Scala that better suited for such large in-memory > data processing. > > Thank you!
It sounds like you're running out of executable memory, not heap space. Try upping --max_executable_size. You may want to investigate why you're running out of executable memory. It might indicate a resource leak in your application somewhere. -- -- 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.
