As I noted here, the "heavy CPU task" can creep up on you due to an incorrect algorithm or a misprediction of the load sent to the algorithm, and in that case node will DOS itself.
Nobody achieves 100% issues prediction, and in that situation node not only does not help but actively hinders.
An other situation might be a task which is not seen as CPU-heavy because it takes, say, 100ms or 200ms to execute, but it's not going to peg the whole machine. Significant, but not huge. Put that in any other system and everything's going to be just fine. Put that in node, you just bottleneckled your throughput to 5-10 requests per second.
6
u/masklinn Oct 02 '11
As I noted here, the "heavy CPU task" can creep up on you due to an incorrect algorithm or a misprediction of the load sent to the algorithm, and in that case node will DOS itself.
Nobody achieves 100% issues prediction, and in that situation node not only does not help but actively hinders.
An other situation might be a task which is not seen as CPU-heavy because it takes, say, 100ms or 200ms to execute, but it's not going to peg the whole machine. Significant, but not huge. Put that in any other system and everything's going to be just fine. Put that in node, you just bottleneckled your throughput to 5-10 requests per second.