{"id":9636,"date":"2013-02-25T12:11:18","date_gmt":"2013-02-25T06:41:18","guid":{"rendered":"https:\/\/2thenew.online\/blog\/?p=9636"},"modified":"2013-02-25T12:18:24","modified_gmt":"2013-02-25T06:48:24","slug":"clustering-in-node-js","status":"publish","type":"post","link":"https:\/\/2thenew.online\/blog\/clustering-in-node-js\/","title":{"rendered":"Clustering in Node.js"},"content":{"rendered":"

Node.js<\/strong> is single threaded so it runs one process on a single CPU<\/strong>, as the power of Node.js<\/strong> is its performance and speed it doesn’t seem good to use only one CPU<\/strong> in a multi-core system. For utilizing all the CPUs<\/strong>, Node.js<\/strong> allows us to create a network of processes that all shares the same port.<\/p>\n

\n

Create a file named clusterExample.js<\/strong><\/p>\n

[js]
\nvar cluster = require(‘cluster’); \/\/use the cluster module
\nvar http = require(‘http’)
\nvar noOfCPUs = require(‘os’).cpus().length(); \/\/count the no of CPUs available<\/p>\n

if (cluster.isMaster) { \/\/Check if the cluster is master or worker process
\n for (var i = 0; i < noOfCPUs; i++) {
\n cluster.fork() \/\/creates a worker process
\n }<\/p>\n

\/\/give message on console when worker process starts listening
\n cluster.on(‘listening’, function (worker, address) {
\n console.log("A new worker process with #" + worker.id + " is now listening to " + ":" + address.port);
\n });<\/p>\n

\/\/give message on console and create a new worker porcess when a worker process dies
\n cluster.on(‘exit’, function (worker, code, signal) {
\n console.log("worker process with #" + worker.process.pid + "died");
\n cluster.fork(); \/\/create the new worker process
\n });
\n} else {
\n http.createServer(function (req, res) {
\n res.writeHead(200);
\n res.end("Cluster Example\\n");
\n }).listen(9090);
\n}
\n[\/js]<\/p>\n

Now run the clusterExample.js<\/p>\n

[js]node clusterExample.js[\/js]<\/p>\n

Output:<\/h3>\n

A new worker process with #1 is now listening to :9090
\nA new worker process\u00a0with #2 is now listening to :9090
\nA new worker process\u00a0with #3 is now listening to :9090
\nA new worker process\u00a0with #4 is now listening to :9090<\/p>\n

\n

Shreyance Jain
\nshreyance@intelligrape.com<\/a><\/p>\n

\n","protected":false},"excerpt":{"rendered":"

Node.js is single threaded so it runs one process on a single CPU, as the power of Node.js is its performance and speed it doesn’t seem good to use only one CPU in a multi-core system. For utilizing all the CPUs, Node.js allows us to create a network of processes that all shares the same […]<\/p>\n","protected":false},"author":64,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":9,"footnotes":""},"categories":[1],"tags":[1137,1138,1124],"class_list":["post-9636","post","type-post","status-publish","format-standard","hentry","category-technology","tag-cluster","tag-cpu","tag-node-js"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t