node

Engine · JS · engine: node:http

Node's own HTTP server, node:http, with no framework and no dependencies, and one worker per core sharing the port through reusePort.

Composite rank

Each profile of a family is worth 100 to the entry that leads it, and the composite is the sum over the family. The field is this entry's own league: engines and reverse proxies are scored apart from frameworks. How it works.

Family	Rank	Composite
HTTP/1.1	28 of 34	48

Every result

Alpha Round, 12 runs. Requests per second is the best of three; latency, CPU and memory come from that run.

Category	Profile	Conns	Req/sec	Avg	p99	CPU	Memory
Connection	Baseline	512	907,802	563us	1.34ms	6679.8%	1.5GiB
Connection	Baseline	4,096	892,087	4.60ms	6.22ms	6553.9%	1.6GiB
Connection	Pipelined	512	1,848,457	4.43ms	7.68ms	6669.2%	2.3GiB
Connection	Pipelined	4,096	1,837,282	35.61ms	44.90ms	6553.1%	2.5GiB
Connection	Short-lived	512	747,342	676us	6.80ms	6187.4%	5.3GiB
Connection	Short-lived	4,096	768,440	5.30ms	87.50ms	6415.9%	5.4GiB
Workload	JSON	4,096	713,493	5.40ms	152.50ms	6393.6%	5.0GiB
Workload	JSON Comp	512	281,475	1.81ms	6.96ms	5817.4%	8.9GiB
Workload	JSON Comp	4,096	289,309	13.78ms	325.60ms	6307.9%	9.0GiB
Workload	JSON Comp	16,384	285,229	50.17ms	1.32s	6180.5%	9.5GiB
Workload	Upload	32	2,058	15.48ms	78.90ms	2462.3%	5.3GiB
Workload	Upload	256	2,156	115.53ms	656.70ms	5931.9%	5.6GiB

Compared with

The JS entries around node on the HTTP/1.1 composite, and the one leading them. The last column shows every profile side by side.

Entry	Composite	vs node
fulmine	769	+1492%	head to head
node-h3	207	+328%	head to head
koa	146	+201%	head to head

Compare node with any JS entry · Every JS entry, ranked

Results updated 2026-08-19 · How the benchmark is run · The machine · Add or fix an entry