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

41–45 of 45 posts

Re: Node.js Has 1 Gb Memory Limit

#41

Post by nivertech »

jat850 wrote: post #40
nivertech wrote: post #39

Earlier quoted context omitted.

If you have 140M active users, handling a fleet of 1000 servers is not an easy operation, considering you need to manage inter-cluster communications (i.e. when sender and receiver sockets fell on different servers). I've built Erlang/OTP websockets clustered server, which can handle 3M per node (giving you have enough RAM). Here you handle all your users with "only" 47 servers. There is a big operational and scaling…

I'm a bit curious about this. If you have 140M concurrent users (since this was the original complaint) and you are NOT prepared or capable of servicing/monitoring/maintaining 1000 servers, that seems like a fatal flaw in your server management and analytics processes. Certainly 47 servers vs. 1000 is far nicer. But at 140M concurrent users levels (there must only be a few handfuls of sites with these types of concer…

The problem is not only operational, but also a technical one:

Nodes in the cluster need to communicate with each other and with other systems, like databases, message queues, monitoring servers, etc.

You can aggregate data per node, so the less servers in the front-end cluster you have, the less load on the back-end servers.

There is also financial problem: many organizations can afford 50 servers. But not many can afford 1000 servers.

Re: Node.js Has 1 Gb Memory Limit

#42

Post by ellyagg »

irahul wrote: post #38
tuukkah wrote: post #29

Earlier quoted context omitted.

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

That's news to me. Language follows speakers, especially influential speakers, and the list of speakers using that for human antecedents includes Shakespeare and Mark Twain, so I guess it's all right now, even if it were an error at some point(grammar isn't static - it has been changing ever since it came into being). Now I am wondering about why I thought that isn't to be used for human antecedents. Was it an error…

You probably thought that because it's uncommon in good writing and you're taught not to do it. It's probably against style guidelines for major newspapers, for example, and it sounds elegant to educated native writers.

Re: Node.js Has 1 Gb Memory Limit

#43

Post by axiak »

nivertech wrote: post #41
jat850 wrote: post #40

Earlier quoted context omitted.

I'm a bit curious about this. If you have 140M concurrent users (since this was the original complaint) and you are NOT prepared or capable of servicing/monitoring/maintaining 1000 servers, that seems like a fatal flaw in your server management and analytics processes. Certainly 47 servers vs. 1000 is far nicer. But at 140M concurrent users levels (there must only be a few handfuls of sites with these types of concer…

The problem is not only operational, but also a technical one: Nodes in the cluster need to communicate with each other and with other systems, like databases, message queues, monitoring servers, etc. You can aggregate data per node, so the less servers in the front-end cluster you have, the less load on the back-end servers. There is also financial problem: many organizations can afford 50 servers. But not many can…

There's no reason why you can't have many node processes per server. This also raises the fault tolerance per server.

Re: Node.js Has 1 Gb Memory Limit

#44

Post by nivertech »

axiak wrote: post #43
nivertech wrote: post #41

Earlier quoted context omitted.

The problem is not only operational, but also a technical one: Nodes in the cluster need to communicate with each other and with other systems, like databases, message queues, monitoring servers, etc. You can aggregate data per node, so the less servers in the front-end cluster you have, the less load on the back-end servers. There is also financial problem: many organizations can afford 50 servers. But not many can…

There's no reason why you can't have many node processes per server. This also raises the fault tolerance per server.

Facebook chat has only 38 gateway servers. I guess, that only possible b/c not every active facebook user, uses Chat.

Re: Node.js Has 1 Gb Memory Limit

#45

Post by flexd »

nivertech wrote: post #44
axiak wrote: post #43

Earlier quoted context omitted.

There's no reason why you can't have many node processes per server. This also raises the fault tolerance per server.

Facebook chat has only 38 gateway servers. I guess, that only possible b/c not every active facebook user, uses Chat.

Perhaps they should consider adding more, it's permanently screwed up in some way. Messages not being sent or the other person not receiving them.
Post reply on HN