Update crates.io package

[cfsamson]

Hi. I’m writing on an article about do’s and dont’s in aync Rust and using actix as an examle. I wanted to use a Rust load testing application for benchmarking different changes and it led me to Drill which is a really nice tool.

However, it took som time before I found out that benchmark.yaml expected “threads” instead of “concurrency” since all the examples uses that. The only hint is to look at the gif and pause it to see the right configuration. Also there seems to be som progress on performance that would be great to get when using cargo install.

[fcsonline]

Glad to read this. Whatever feedback about async will be awesome.

However, it took som time before I found out that benchmark.yaml expected “threads” instead of “concurrency” since all the examples uses that. The only hint is to look at the gif and pause it to see the right configuration. Also there seems to be som progress on performance that would be great to get when using cargo install.

About this, I just want to say that we are right in the middle of the transition between threads and full async configuration. Few weeks ago we merged the first async implementation of drill and now we are doing small improvements to complete the transition. If you review this pull request ( https://github.com/fcsonline/drill/pull/61 ) you will see that we are trying to get rid of the threads configuration towards concurrency configuration. As soon as we consider that everything is stable and we perform the maximum throughput, we will release a new version and publish it to crates.io. If you want to take a look and give some feedback, feel free.

[cfsamson]

Oh, I see. That sounds great. I just browsed through and it looks like you're well on the way. I'll see if I have time to dig deeper into this after I finish what I'm currently working on. The problem of keep alive and having a global pool of connections seems interesting though, and I guess that's important for maximum throughput as well?