Built-in clustering mode (automatic / flagged)

[waqasmughal]

why not add built in clustering mode rather than manual . like node auto detect no of cpus and utilize all cpu cores . or better to integrate node-threads-a-gogo as core for hybrid app
https://github.com/xk/node-threads-a-gogo

[cjihrig]

@waqasmughal what do you envision this looking like? How would you distinguish between the cluster master and workers? I'm wary of introducing too much magic - cluster already does a lot of things under the hood.

Regarding workers, there is an initial PR to add them to core in #2133.

[Fishrock123]

Would this be better as an npm module?

I think there's a larger thing behind this where adding what is most convenient / intuitive to core isn't necessarily what is good or sustainable for Node.js. :s

better docs?

[cjihrig]

What would you change in the docs? I don't think this would be a good thing to have in core, but wanted to hear @waqasmughal's thoughts first.

[waqasmughal]

Hi ,
Thanks for your response . I am new to node.js .
what about if i have request which takes almost 10 sec to resolve and send back response after 10 sec . All remaining request are in queue and server would block even i have callbacks . the solution is parallel processing but that violate node behavior . If we create child process which deal only blocking part also resolve our problem but it's memory limitation issue .(like we have 10000 concurrent requests so 10000 process start ).

For Example
var http = require("http");
var url = require("url");

http.createServer(function(request, response) {

if (url.parse(request.url).pathname == '/long')
{
    function longlong()
    {
        var counter = 0;
        var startTime = new Date().getTime();
        while (new Date().getTime() < startTime + 10000)
        {
            counter++;
        }
        return counter;
    }

    response.writeHead(200, {"Content-Type": "text/plain"});
    response.write(longlong() + '');
    response.end();
}
else
{
  response.writeHead(200, {"Content-Type": "text/plain"});
  response.write(0 + '');
  response.end();
}

}).listen(8888);

[cjihrig]

Welcome to Node! We do just about everything asynchronously over here (meaning you don't need to spawn a bunch of server processes like you would in Java). Your long running task should be done asynchronously to avoid blocking your server. Built in clustering wouldn't really help here. The cluster module just spawns child processes, which you've already said isn't an option.

If you want help architecting your project, you might want to ask over at https://github.com/nodejs/help. I'm going to close this for now.