4 ms·
Server issues. Let me guess: node.js?
by blue_spice 14y ago
Server issues. Let me guess: node.js?
- mojuba 14y agoApparently yes: https://github.com/n01se/1110 https://github.com/n01se/1110
- blue_spice 14y agoThanks. Not surprised.
- SquareWheel 14y agoAnd I bet they use HTTP, too. Pfft. It's easy to confirm biases against wide-spread technologies.
- bduerst 14y agoHTTP is a teensy tiny bit more used than node.js
- user24 14y agoYou say that like node is known for being flaky at scale, which is completely unfounded.
- reinhardt 14y ago... and MongoDB.
- deleted 14y ago[deleted]
- Tipzntrix 14y agoHey, it's web scale
- manuscreationis 14y agoDo you think the server would perform more effectively if they had enabled the Cluster configuration (assuming the server has multiple cores)? I'm fairly new to toying around with Node, so i'd be interested to know if there are fairly obvious or simple reasons for poor performance here
- ville 14y agoLooks like the maximum number of clients is limited to 20 in the code: https://github.com/n01se/1110/blob/master/server.js#L44 https://github.com/n01se/1110/blob/master/server.js#L44
- user24 14y agothat would certainly help but it's just not running on a very powerful server, it's nothing to do with the language.
- manuscreationis 14y agoMakes sense
- mojuba 14y agoIt's nothing to do with the language, it's to do with the threading model. It's a much argued about topic nowadays: one approach give peace of mind to programmers, and the other one gives peace of mind to users.
- chrishouser 14y agonode.js on a ti-micro. Just not much horsepower on the back end.