Mchakato mmoja wa Node.js hutumia kiini kimoja cha CPU tu (JS yake inaendesha kwenye nyuzi moja). Ili kutumia viini vyote kwenye injini, unacheza michakato mingi ya Node.js — kupitia moduli ya cluster, meneja wa michakato kama vile PM2, au uratibu wa kontena — na kusambaza matakwa kwa uzani kati yao.
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);
}
Mchakato mkuu unafuata mfanyakazi mmoja kwa kila kiini; wafanyakazi wote wanashiriki bandari sawa, na uunganisho unaoingia unasambazwa kati yao — kuzidisha kasi. Wafanyakazi walio na matatizo yanaweza kuanzishwa tena kiotomatiki kwa uimara.
pm2 start app.js -i max # run one instance per CPU core, with auto-restart & monitoring
Programu za uzalishaji kawaida hutumia PM2 (au kilicho sawa) badala ya kuandika nambari za cluster kwa mikono — inahakikisha forking, kusambaza uzani, kuandika tena bila wakati wa kutu, kufuatilia, na kuanzisha tena.
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
Kwa ajili ya kuongeza kiwango cha michakato mingi ili kufanya kazi, programu yako lazima iwe bila hali — hali yoyote iliyoshirikiwa (vipindi, kache, uratibu wa wakati halisi) lazima iwe katika hifadhi ya nje kama Redis, si katika kumbukumbu ya mchakato.
Kutumia viini vyote vya CPU ni muhimu ili kupata utendaji kamili kutoka kwa seva ya Node — mchakato mmoja unaacha karibuni vyote vya injini yenye viini vingi bila kazi.
Kujua chaguo (moduli ya cluster, njia ya cluster ya PM2, au mchakato mmoja kwa kontena na uratibu) na, muhimu sana, haja ya kuwa na hali yenye utata (vipindi/kache/wakati halisi na msaada wa Redis, kwa sababu michakato haisambazani kumbukumbu) ni msingi wa kuongeza kiwango cha Node katika uzalishaji.
Kuongeza kiwango kwa usawa, kukumbatiana na kuwa na hali yenye utata, ndilo njia ambayo programu za Node zinavyoshughulikia trafiki ya juu kwa kutegemeka.