Cluster with uWebSocket

[yovanoc]

Hello, follow up of my message on #214 I just want to know how to make it work because when I done that:

import cluster from "cluster";
import { cpus } from "os";

const numCPUs = cpus().length;

function masterProcess() {
  console.log(`Master ${process.pid} is running`);

  for (let i = 0; i < numCPUs; i++) {
    console.log(`Forking process number ${i}...`);
    cluster.fork();
  }
}

function childProcess() {
  console.log(`Worker ${process.pid} started...`);

  app
    .any("/*", res => {
      /* Let's deny all Http */
      res.end("Nothing to see here! (" + process.pid + ")");
    })
    .listen(serverPort, listenSocket => {
      if (listenSocket) {
        log(`Listening to port ${serverPort}`);
      }
    });
}

if (cluster.isMaster) {
  masterProcess();
} else {
  childProcess();
}

I always get the same PID, I don't know why, I just tested with a simple httpServer include with node and it works, so can it really works like that?

Sorry for my noobiness :x

[ghost]

I get different pid. You probably get the same because your browser keeps the same connection. Try with curl and you'll see different pids.

[yovanoc]

I've already test it.... so i'ts my computer who give me always the same because is not "stressed" enough to load balance to another?

[yovanoc]

Sorry to comment again but is the app.listen function who have to be in the childProcess or all app.get, app.ws, etc too? thanks

[yovanoc]

Sorry @alexhultman , but can I have an answer on my last question?

[ghost]

Everything has to be in child, the entire app should be isolated per process or per thread

[yovanoc]

Yes I see now why, great thanks, but I really don't know how to do this with a clean architecture since I have a lot of routes http and ws

[taehyeong224]

I got the same PID with a similar code in macOS Catalina. but I got the different PID in ubuntu 16.04.

[ghost]

Clustering is a Linux feature, it does not work on Windows or macOS. You'll get different PIDs when you stress the server on Linux.

[animaonline]

@alexhultman forking the process several times in order to "create a cluster" is pretty common in nodejs, it works on all platforms, on Linux and macOS TCP sockets are shared across forked instances, it works with standard tcp sockets / express and other frameworks, is there a reason why it doesn't work with uWebSockets.js? Does it need to be implemented in the native module?

[e3dio]

Open issue here uNetworking/uWebSockets#1194 I would use the windows cluster if avail, maybe just needs some effort

[animaonline]

@e3dio thanks man