I had a similar problem, with a simple parser that just reads the twitter stream. The initial reading rate declined the longer the process was running while the memory usage grew and grew. The old parser used String.slice(). I rewrote it to use String.split to cut the single JSON objects from the stream API. I am currently running a long test run. Now the rate is climbing (slowly, but climbing) and memory usage is stable
Does someone here know if that is a known problem for node 8.4? So far I did not find anything in the issue list on GitHub. I can provide a test case to reproduce this. -- 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
