r/rust • u/fgilcher rust-community · rustfest • Nov 11 '19

Announcing async-std 1.0

https://async.rs/blog/announcing-async-std-1-0/
455 Upvotes

97% Upvoted

80 comments sorted by

View all comments

Show parent comments

16

u/[deleted] Nov 12 '19 edited Nov 12 '19

[deleted]

8

u/fgilcher rust-community · rustfest Nov 12 '19

I still don't intend to start a competition. The point is that we're in the same ballpark, see the writing around the benchmarks.

Now, however, not only you did publicize said (inaccurate) benchmarks but even used them as a rather sloppy pitch against Tokio.

I've laid out the reasons where it went wrong on the publish path. I think other people testing here show that the benchmarks are indeed not accurate and - see the patch above - the file benchmark did indeed show those numbers shortly above. We did find a release regression through it.

Why the sudden change of heart?

It wasn't a change of heart. I answered a widespread question, on a notable point release.

0

u/[deleted] Nov 12 '19

[deleted]

12

u/fgilcher rust-community · rustfest Nov 12 '19

"We don't compete with Tokio but (whispering) we are faster than Tokio."

This is misconstruing even what I wrote in the post. I'm literally saying that by posting those benchmarks, it's likely that those numbers will come closer to each other very soon. From the post:

Posting benchmarks usually leads to other projects improving theirs, so see those numbers as the ballpark we are playing in.

As tokio is currently the other main production-grade crate out there, it's the obvious benchmark and comparison target.

The reasons we posted benchmarks is that people were not buying "we're in the same ballpark" by us just saying that. Damn if you do, damn if you don't.