[markus_v]

Not sure but it kind of seems like they are running only one (single-threaded) Node process on multicore CPUs.

[wiennat]

This immediately comes into my mind when I see the charts.

It is also interesting to see that only one Node process can barely serve 10k connections.

---- After I check the source at [0]. They use a simple http module to serve the requests while they use `http.ListenAndServe` which spawns go routines, hence more CPU utilization.

[0] https://gitlab.com/stressgrid/dummies

[HiFaraz]

It's an unfair comparison then if they don't even use Node.js to its full potential. Apple to oranges comparison.

[kt315_]

Author here. Planning to run the same test using cluster module with one worker per CPU.

What would be the most performant way to serve HTTP in Go?

[schrodinger]

That’s the idiomatic way to handle requests in Go. What’s the problem?

[theamk]

Maybe they were simulating some sort of messaging server, or a shared cache, or something else which does not translate well to multiple process model?