It would be interesting to hear more about this because with CPU spiking like that I would have expected more variability in the response time...but quite the opposite it was the most consistent which is one of the big things that the BEAM aims for.

I wonder if somebody who's more of an expert on the BEAM could chime into why that might be. More activity in the scheduler maybe?

Re: Benchmarking Go vs. Node vs. Elixir

#33

Post by Juliennng » Tue, Feb 12, 2019, 12:31 AM UTC

hactually wrote: post #6

someguy101010 wrote: post #4

Tldr?

Node bad, Elixir good but spikey on the CPU, Go best.

It seems the Elixir CPU usage is due to the way the Erlang VM manages schedulers. A scheduler will literally busy-wait if it thinks there might be more work to do soon, in an effort to improve the responsiveness of the system

Post reply on HN