node-tick icon indicating copy to clipboard operation
node-tick copied to clipboard

process out of memory

Open flaviotorres opened this issue 10 years ago • 5 comments

Hello,

I'm trying to process the v8, but I'm getting this message after ~ 30 minutes:

node-tick-processor --ignore-unknown --unix v8-30834.log|tee v8-30834.out

FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory

The process node-tick uses 100% of CPU and almost 40% of memory.

File: v8-30834.log, 646M Nodejs version: node-v0.10.36-linux-x64 CentOS release: 6.6 Memory: 4G VMWare, 4CPUs Intel(R) Xeon(R) CPU E5-4620 0 @ 2.20GHz

Server haven't swapped out.

Am I missing something?

Thank you,

flaviotorres avatar Aug 01 '15 02:08 flaviotorres

this module processes log file as stream line by line, and I tried it with log files 2-3 Gb big, so this is a bit surprising. Can you upload zipped log file somewhere and post link here? ( if there is something you don't want to expose you can send me link via email - [email protected] . I think only function names are visible in the log file )

sidorares avatar Aug 03 '15 00:08 sidorares

Hi,

Just got my files processed by adding 'max-old-space-size', ex: $ node --max-old-space-size=6144 /opt/nodejs/bin/node-tick-processor --ignore-unknown --unix v8-30838.log

Also, I've sended to you an email with instructions to download my file and test against it.

Thank you for your quick reply. Regards,

flaviotorres avatar Aug 06 '15 03:08 flaviotorres

hi! Sorry for silence. Tried your file some time ago and it does indeed take a lot of ram ( ~1.7G ) but finishes successfully after approx 10 minutes. Tried it with iojs 2.3.1

sidorares avatar Aug 06 '15 03:08 sidorares

I guess I'll need to profile profiler :)

sidorares avatar Aug 06 '15 03:08 sidorares

What worked for me was as @flaviotorres said, adding the --max_old_space_size flag

tsirolnik avatar Jan 04 '17 08:01 tsirolnik