News for hackers. Stuff that matters.
Re:Node.js cures cancer by billconan on Monday October 03, 2011 @02:54AM (#3065340)
The article uses two examples to demonstrate that v8 is in fact fast. However, when using python or ruby to create a web server, the server will actually run in parallel (multiple threads), therefore, the average waiting time could be less than the node.js version.
Re:Node.js cures cancer by billconan on Monday October 03, 2011 @02:59AM (#3065349)
suppose, for example, we have two people connecting to the server at the same time. if it is the node.js server, one person waited for 5 seconds, the other one waited for 10 seconds, the average waiting time is (5+10) / 2 = 7.5

assume that the python server is less efficient, which takes 7 seconds to finish the job. but it runs in parallel. so both two people waited 7 seconds.

therefore, on average, the python server is in fact, faster

Re:Node.js cures cancer by billconan on Monday October 03, 2011 @03:02AM (#3065355)
i am not a node.js expert. one thing i am wondering is that, modern computers have more than just one core. how node.js utilizes these multiple cores?
Re:Node.js cures cancer by ricardobeat on Monday October 03, 2011 @03:15AM (#3065378)
By starting multiple processes.

See cluster (https://github.com/LearnBoost/cluster), fugue (https://github.com/pgte/fugue), multi-node (https://github.com/kriszyp/multi-node)

Re:Node.js cures cancer by aliem on Monday October 03, 2011 @08:36AM (#3066028)
This is true for Python, Ruby, PHP. (I can't see ted's issues with node other than misunderstanding of the framework's runtime)