Question: Idiomatic usage for high-throughput POST benchmark client

[InfiniteConsult]

Hello Reqwest community,

I'm currently working on a project comparing HTTP client performance across C++, Rust, C, and Python, available here:
https://github.com/InfiniteConsult/0004_std_lib_http_client

I've included Reqwest (using the blocking client) as a Rust baseline for comparison. The benchmark harness code is located here:
https://github.com/InfiniteConsult/0004_std_lib_http_client/blob/main/src/rust/src/bin/reqwest_client.rs

The benchmarks focus on high-throughput POST requests (varying sizes) over a persistent connection. The results show Reqwest performing reasonably well.

My primary goal is to ensure a fair comparison between the libraries. With that in mind, I wanted to ask if the implementation in the linked harness (reusing the reqwest::blocking::Client, sending POST requests in a loop) reflects an idiomatic and efficient approach for this specific task within Reqwest's design. Are there any obvious performance anti-patterns or standard practices I should be aware of to represent Reqwest fairly?

Thanks for any feedback and for developing Reqwest!

Regards,

Warren Jitsing