Ciro's `nc` HTTP test server

As per stackoverflow.com/a/52351480/895245 our standard test setup is:

while true; do
  resp=$"$(date): hello\n"
  len="$(printf '%s' "$resp" | wc -c)"
  printf "HTTP/1.1 200 OK\r\nContent-Length: $len\r\n\r\n${resp}\n" | nc -Nl 8000
done

Node (server)

0 0

It runs one instance of the Linux kernel and has one IP address. Each node is therefore a complete computer. As such is must also contain RAM memory, disk storage and a network interface controller.

CPUs per node and nodes per server (server)

0 0

there can be more than one node per server.
there can be more than one CPU per node

E.g.:

Frontier:
- 2 nodes per blade, 1 CPU per node. Therefore 1 CPU per node.

Blade server

0 0

Video 1.

HP Blade Server by Brian Kirsch (2013)

Source.

Featuring an HP DL380 blade server, presumably an older model of this series: buy.hpe.com/uk/en/servers/proliant-dl-servers/proliant-dl300-servers/proliant-dl380-server/hpe-proliant-dl380-gen10-server/p/1010026818.

In the video we can see that it contains RAM, disk storage, we are told about two CPUs, and networking interfaces, so it is a complete computer on its own. He also explains that unlike typical rack servers, each blade unit does not have its own coolers and power supply related hardware, which goes instead on the chassis.