News for hackers. Stuff that matters.
Re:Rust async-await status report 2 by steveklabnik on Wednesday July 10, 2019 @10:25AM (#20402225)
While it is true that I'm mostly talking about computation speed, that's not the only thing. It is true that Erlang is good at this, but I'd like to see some real numbers here. In benchmarks, this is almost never the case. For example, if you take a look at techempower's plaintext benchmark, which should purely be about IO: https://www.techempower.com/benchmarks/#section=data-r18&hw=...

Phoenix, which is in Elixir, does 2.7% of the requests of the Rust frameworks. Chicago Boss, in Erlang, does 0.2%. Is this a realistic benchmark? I don't know; I can't say if the code for either of these implementation is good or not. But if it's a silly error, I think it would be good for Elixir/Erlang advocates to fix this. Early Rust implementations had extremely poor showings too.

I tend to think of Erlang as being extremely reliable, with acceptable performance, rather than being the fastest IO language in the West.

Re:Rust async-await status report 2 by di4na on Wednesday July 10, 2019 @11:08AM (#20402659)
As an admin of the elixir slack, i have to handle that one a lot.

It is not really realistic at all no. But mostly because the benchmark is not realistic of a production load. That said we should do better.

The main reason it is not fixed is that the few members of the community that tried to fix it had a really bad experience interacting with the repo and getting feedback of impact and simply lost interest. And we have not have people motivated enough so far because they do not really care about the benchmark.

Ofc it matters to people that are not in the community but well...

That said, yes we would never be close to Rust anyway (probably) but we could probably have a far better standard deviation than Rust. Something that tend to matter in production a lot but people forget reading benchmark is the spread of the response time vs the average one.

We should also perform better in a noisy environment like the "cloud" one.

There are hopes that the recent EEF marketing group could help find volunteers or finance someone to fix it.

Re:Rust async-await status report 2 by steveklabnik on Wednesday July 10, 2019 @11:13AM (#20402738)
Yep, that makes perfect sense. I've had good experiences contributing, but it can be tough...

It's also 100% true that benchmarks are not representative of production loads. Sadly, it's also 100% true that programmers make decisions based on benchmarks that aren't representative of production loads. It's a real catch-22 situation.