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

11–20 of 45 posts

Re: Node.js Has 1 Gb Memory Limit

#11

Post by andreyvit »

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.

My line of thought is that V8 is used in Node.js and in the browser, but 1 Gb is unlikely to be a problem for the browser any time soon, so it's really only a problem for Node.js. Am I missing something?

Re: Node.js Has 1 Gb Memory Limit

#12

Post by jrockway »

joezydeco wrote: post #9
russellallen wrote: post #8

Earlier quoted context omitted.

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 browser you huge 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.

The moral of the story is to never be nice to anyone. Nobody complains about the memory limits of IE's javascript engine as they pertain to server-side applications.

Re: Node.js Has 1 Gb Memory Limit

#16

Post by mjijackson »

It would be more correct to say that V8 has a 1G memory limit. But node.js actually gives you these nice things called Buffers which, according to the node.js manual, are "similar to an array of integers but corresponds to a raw memory allocation outside the V8 heap" (see http://nodejs.org/api/buffers.html).

Buffers are used all over the place in node, which should mitigate the degree to which this is actually a problem. Even if this bug report stays a wontfix, it won't affect my decision to use node because of Buffer support.

Re: Node.js Has 1 Gb Memory Limit

#17

Post by moomin »

There's a general point to be made here: this is the sort of thing that happens when you have "closed development open source". Admittedly, there seem to be very few people in the world capable of delivering a world-class GC.

Re: Node.js Has 1 Gb Memory Limit

#19

Post by ww520 »

eric-hu wrote: post #5

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

I don't understand why he has to stop the project just because ONE node.js process cannot handle more than 140K concurrent connections. If the goal is to handle millions of concurrent connections, spreading the connection load out to multiple servers is a must.

I'm doing something similar with node.js now to handle millions of concurrent connections. I use multiple node.js servers to handle it. Not only it helps in even out the load, it has the nice failover property. One node down doesn't mean the whole app is down. Clients of the down node migrate their connections to the rest of the nodes.

Post reply on HN