Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Node.js Has 1 Gb Memory Limit

code.google.com

Post reply on HN
Print view View original

1–10 of 45 posts

Re: Node.js Has 1 Gb Memory Limit

#3

Post by andreyvit »

To add my own perspective: I was running some analytics batch job on Node and hit this limit, had to add multi-stage processing to accommodate it. Using --max-old-space-size=1900 did help a bit.

In case you're wondering, here's a test case: https://gist.github.com/1148761

I was told by one of the V8 developers that the new GC is pretty usable now, so worth giving it a shot if you need more than 2 Gb.

Re: Node.js Has 1 Gb Memory Limit

#5

Post by eric-hu »

Relevant snippets:

"diego.ca...@gmail.com, Sep 19, 2010

... In my case, I've been forced to suddenly stop my work ... with node.js because it cannot handle more than ~140K websockets concurrent connections ..."

"erik.corry, Nov 2, 2010

The limit for 64 bit V8 is around 1.9Gbytes now. Start V8 with the --max-old-space-size=1900 flag."

Re: Node.js Has 1 Gb Memory Limit

#9

Post by joezydeco »

russellallen wrote: post #8
andreyvit wrote: post #4

Earlier quoted context omitted.

Yep, but the reason we care about it is exactly because it affects Node.

The reason you care about it is because it affects Node. I'm more interested in V8 than Node to be honest.

No doubt. This comment really struck me as off-tone:

"Sorry, Google, but your open-source project is important to much more of the world than just >your browseryouhuge

You know Google is biting their tongue at what they really want to say to complainers like this. You really want it working for Node? Roll up your sleeves and get to refactoring. Hell, they even explained how to fix it.

Post reply on HN