I guess the point of posting it here is to gather folks with pitchforks and torches demanding immediate attention to the issue. For a few months V8 team has been working hard on improving the GC (http://code.google.com/p/v8/source/browse/branches/experimen...) which was the major limiting factor here. I don't have an ETA of when it's going to be merged, but the new GC branch is in a pretty good shape.
Node.js Has 1 Gb Memory Limit
21–30 of 45 posts
Re: Node.js Has 1 Gb Memory Limit
#22What rude and demanding bug reports.
Welcome to Web 2.0, where people that think they're programmers try to interact with people that are programmers. The results are often ... depressing.
A minor re-formatting.
> Welcome to Web 2.0, where people who think they're programmers try to interact with people who are programmers. The results are often ... depressing.
I was confused by your initial framing of the sentence, though my not being a native speaker would have played a part.
Re: Node.js Has 1 Gb Memory Limit
#23nice FUD headline
Why? It's been a real bummer for me to find that out (the hard way).
Why? It's been a real bummer for me to find that out (the hard way).
Knowing about the limit is hurting you, or you have really faced this constraint in a project? As mentioned elsewhere, node has buffers which are allocated outside of v8 heap, and the user data will largely be unaffected by the memory limit if you are using buffers.
Re: Node.js Has 1 Gb Memory Limit
#24Earlier 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.
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?
The 1GB of today was the 128MB of yesterday. I'm guessing in a year or two, games implemented on webgl will be a step up from farmville and require more than 1GB of memory to run well. IE9 still has a chance to catch up if they end up becoming the goto browser for gaming.
And technically the memory issue has already been resolved if you read the comments in the bug posting. The next GC release won't have any of these drawbacks. So really the problem is isolated to any node projects currently in production.
Re: Node.js Has 1 Gb Memory Limit
#25Earlier quoted context omitted.
Welcome to Web 2.0, where people that think they're programmers try to interact with people that are programmers. The results are often ... depressing.
A minor re-formatting. > Welcome to Web 2.0, where people who think they're programmers try to interact with people who are programmers. The results are often ... depressing. I was confused by your initial framing of the sentence, though my not being a native speaker would have played a part.
Yeah, though not really "correct", it's very common to use "that" as a relative pronoun for a person instead of "who". Some pedants may correct you, but it's rare for native English speakers to actually be confused by it.
Re: Node.js Has 1 Gb Memory Limit
#26Relevant 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 e…
You're spot on. I think a lot of people can't wrap their head around node: It's all about scaling horizontally (lots of processes, many servers) rather than vertically (one process with lots of threads on one big server). Once you realise that, it makes a lot of sense.
Re: Node.js Has 1 Gb Memory Limit
#27Earlier quoted context omitted.
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 e…
You're spot on. I think a lot of people can't wrap their head around node: It's all about scaling horizontally (lots of processes, many servers) rather than vertically (one process with lots of threads on one big server). Once you realise that, it makes a lot of sense.
Exactly. I pick Node.js not because one process can handle lots of connections, but because one process can handle lots of connections with low resource utilization. It needs less servers to get the job done. It's more of a cost-based decision.
Re: Node.js Has 1 Gb Memory Limit
#28Earlier quoted context omitted.
Why? It's been a real bummer for me to find that out (the hard way).
Why? It's been a real bummer for me to find that out (the hard way). Knowing about the limit is hurting you, or you have really faced this constraint in a project? As mentioned elsewhere, node has buffers which are allocated outside of v8 heap, and the user data will largely be unaffected by the memory limit if you are using buffers.
I've tried to explain it in another comment:
> 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.
So yeah, it did affect me, although not on a typical web project. It wouldn't be a problem at all if I knew about this limit from the start. Thus this is a warning for others.
(BTW another limit I was told about is that objects can't have more than a million keys. Thankfully I did not hit that one.)
Re: Node.js Has 1 Gb Memory Limit
#29Earlier quoted context omitted.
Welcome to Web 2.0, where people that think they're programmers try to interact with people that are programmers. The results are often ... depressing.
A minor re-formatting. > Welcome to Web 2.0, where people who think they're programmers try to interact with people who are programmers. The results are often ... depressing. I was confused by your initial framing of the sentence, though my not being a native speaker would have played a part.
Hope this helps: "[T]his distinction applies only to which and who. The alternative that is found with both human and non-human antecedents." http://en.wikipedia.org/wiki/English_relative_clauses#Human_...
Re: Node.js Has 1 Gb Memory Limit
#30What rude and demanding bug reports.
Welcome to Web 2.0, where people that think they're programmers try to interact with people that are programmers. The results are often ... depressing.
I don't think the bad bug reports have anything to do with whether or not the petitioner is a programmer.