3 ms·

Yeah it's complete bs. I've worked on chat before and even 100 clients destroy a core or even two. Now I would use pusher but that's extremely expensive but sc

by homero 10y ago

Yeah it's complete bs. I've worked on chat before and even 100 clients destroy a core or even two. Now I would use pusher but that's extremely expensive but scalable.

segmondy 10y ago
100 clients destroying a core or two? Please, use the right tool. See erlang, golang, java, even c#. Years ago, you had to suffer using poll(), select(), whilst dealing with threads or forking. It's so easy these days. A raspberry pi should be able to support 1,000 clients with any of the above recommended languages.
Swennemans 10y ago
That seems unnecessary. Or did you use (something like) Meteor.js?
angersock 10y ago
Yeah, no, that's wrong. If you have problems with this, there's something really wrong with either your design or your choice of tools. How'd you go about building this?
- homero 10y ago
  In 2008 with php and ajax
tracker1 10y ago
Node was designed to hit 100K users/core, and in fact can do closer to 1M users... for simpler chat relay, a single server should be able to handle 1M simultaneous users... Growing beyond that means you need to segment/orchestrate your channels. I haven't used the app to comment... but something written in golang could probably handle a couple million users on a single server via websockets (or raw sockets), with appropriate backing services in place. The original article is condescending to say the least, that doesn't mean that $4k of ongoing hosting costs shouldn't be able to handle a few million simultaneous users... though, something tells me that Pokemon Go could approach twitter or FB overhead, and related apps like chat could see huge swarms as a side effect. That kind of problem would kill most first generation apps, as those who've seen twitter grow can attest to. I don't think there are any IRC networks that big at this point.

3 ms·

Yeah it's complete bs. I've worked on chat before and even 100 clients destroy a core or even two. Now I would use pusher but that's extremely expensive but sc

by homero 10y ago

Yeah it's complete bs. I've worked on chat before and even 100 clients destroy a core or even two. Now I would use pusher but that's extremely expensive but scalable.

segmondy 10y ago
100 clients destroying a core or two? Please, use the right tool. See erlang, golang, java, even c#. Years ago, you had to suffer using poll(), select(), whilst dealing with threads or forking. It's so easy these days. A raspberry pi should be able to support 1,000 clients with any of the above recommended languages.
Swennemans 10y ago
That seems unnecessary. Or did you use (something like) Meteor.js?
angersock 10y ago
Yeah, no, that's wrong. If you have problems with this, there's something really wrong with either your design or your choice of tools. How'd you go about building this?
- homero 10y ago
  In 2008 with php and ajax
tracker1 10y ago
Node was designed to hit 100K users/core, and in fact can do closer to 1M users... for simpler chat relay, a single server should be able to handle 1M simultaneous users... Growing beyond that means you need to segment/orchestrate your channels. I haven't used the app to comment... but something written in golang could probably handle a couple million users on a single server via websockets (or raw sockets), with appropriate backing services in place. The original article is condescending to say the least, that doesn't mean that $4k of ongoing hosting costs shouldn't be able to handle a few million simultaneous users... though, something tells me that Pokemon Go could approach twitter or FB overhead, and related apps like chat could see huge swarms as a side effect. That kind of problem would kill most first generation apps, as those who've seen twitter grow can attest to. I don't think there are any IRC networks that big at this point.