Proċess Node wieħed juża biss core CPU wieħed (il-JS tiegħu taħdem fuq thread wieħed). Biex tuża l-cores kollha fuq magħina, atteħta multiple Node processes — permezz tal-modulu cluster, process manager bħal PM2, jew container orchestration — u load-balance ir-requests bejnihom.
A server with 8 CPU cores running ONE Node process → uses ~1 core, wastes 7.
Need multiple processes to utilize all cores and handle more concurrent load.
import cluster from "cluster";
import { cpus } from "os";
import http from "http";
if (cluster.isPrimary) {
const numCPUs = cpus().length;
for (let i = 0; i < numCPUs; i++) {
cluster.fork(); // spawn one worker process per CPU core
}
cluster.on("exit", (worker) => {
console.log(`worker ${worker.process.pid} died — restarting`);
cluster.fork(); // restart a crashed worker (resilience)
});
} else {
// each worker runs the actual server; the OS load-balances connections across them
http.createServer((req, res) => res.end("handled by " + process.pid)).listen(3000);
}
Il-proċess primarju jifrek worker wieħed għal kull core; il-workers kollha jaqsmu l-istess port, u l-connections li jidħlu jiġu distribwiti bejnihom — multiplikaw il-throughput. Il-workers li jikkadjraw jistgħu jibdew mill-ġdid awtomatikament għat-tindita.
pm2 start app.js -i max # run one instance per CPU core, with auto-restart & monitoring
L-applikazzjonijiet tal-produzzjoni normalment jużaw PM2 (jew simili) minflok li jiktbu code tal-cluster bil-idejn — jigħoddu il-forking, load balancing, zero-downtime reloads, monitoring, u restarts.
Run ONE Node process per container, and run MANY containers (Kubernetes, ECS),
with a load balancer in front. This is the modern cloud approach — simpler
per-process model, scaling handled by the orchestrator across machines.
Multiple processes don't share memory. So:
⚠️ Don't store sessions/state in process memory → use Redis/a shared store
⚠️ In-memory caches aren't shared across workers → use Redis for shared cache
⚠️ WebSocket connections live on one worker → use a Redis adapter to coordinate
Biex il-multi-process scaling jaħdem, l-app tiegħek għandu jkun stateless — kwalunkwe shared state (sessions, cache, real-time coordination) għandu jvivvi f'external store bħal Redis, mhux fil-memory tal-proċess.
It-tisfruttament tal-cores CPU kollha huwa essenzjali biex tinkiseb full performance minn server Node — proċess wieħed iħalli ħafna minn magħina multi-core idle.
Il-ħarsa tal-għażliet (cluster module, PM2 cluster mode, jew one-process-per-container bi orchestration) u, kruċjalment, ir-rekwiżit ta' statelessness (sessions/cache/real-time fuq Redis estern, billi l-processes ma jaqsmusx memory) huwa fundamentali biex tiskala Node fil-produzzjoni.
Da l-horizontal scaling, flimkien ma' statelessness, huwa kif l-applikazzjonijiet Node jigħoddu traffic għolli b'mod affidabbli.