Ask HN: What are the benefits of using Rust async HTTP clients?

Posted by timhigins on Friday July 03, 2020 @10:50PM
from the ask-hn dept.

Generally it seems like async only has a real benefit when there are many connections.

Is there a scenario where using an HTTP client implemented with Rust's async features gives a substantive performance benefit?

( 2 comments | 2 points | on HN )

Re:Ask HN: What are the benefits of using Rust async HTTP cl... by halffullbrain on Sunday July 05, 2020 @04:48PM (#23741831)

That's correct. With many concurrent connections, you save memory (from thread stacks) and context swiches (since you don't need to switch thread to process each socket).

If all you want is a single request (and you have wait for results to continue work), you don't gain anything by going async.

[ Parent | on HN ]

Re:Ask HN: What are the benefits of using Rust async HTTP cl... by sudeepj on Monday July 06, 2020 @12:46AM (#23744785)

> If all you want is a single request (and you have wait for results to continue work), you don't gain anything by going async

This is true for HTTP version < 2 because of the head-of-line blocking. With HTTP 2 I think a single connection will see a better throughput if not massive increase.

[ Parent | on HN ]