Benchmarking Go vs. Node vs. Elixir

Re:Benchmarking Go vs. Node vs. Elixir by someguy101010 on Tuesday February 05, 2019 @06:44PM (#19091273)

Tldr?

[ Parent | on HN ]

Re:Benchmarking Go vs. Node vs. Elixir by hactually on Tuesday February 05, 2019 @07:48PM (#19091646)

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

[ Parent | on HN ]

Re:Benchmarking Go vs. Node vs. Elixir by Juliennng on Monday February 11, 2019 @07:31PM (#19139920)

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

[ Parent | on HN ]

Re:Benchmarking Go vs. Node vs. Elixir by turbo_fart_box on Wednesday February 06, 2019 @07:19AM (#19094526)

I would love some sort of bot that I could point at blog posts that could summarize articles with the exact language you used.

[ Parent | on HN ]

Re:Benchmarking Go vs. Node vs. Elixir by Madeindjs on Thursday February 07, 2019 @04:46PM (#19108895)

I read article and I saw that Node is not so bad at all..

[ Parent | on HN ]

Re:Benchmarking Go vs. Node vs. Elixir by turbo_fart_box on Wednesday February 06, 2019 @07:18AM (#19094521)

God's work. Thanks

[ Parent | on HN ]