go-wrk[1] promises HTTP/2 support and is similar to wrk. I don't have a lot of experience with it though. [1]: https://github.com/tsliwowicz/go-wrk https://git

go-wrk[1] promises HTTP/2 support and is similar to wrk. I don't have a lot of experience with it though. [1]: https://github.com/tsliwowicz/go-wrk https://github.com/tsliwowicz/go-wrk If you want to purchase advertising for this purpose, I'm happy to help with this. My contact details are linked through my profile. - Your HTTP endpoints will need to be whitelisted with traffic quality groups and creative scanners (This can take a week or so). I recommend using a separate dns domain name for this since adblockers tend to subscribe to these lists. - Your JavaScript should not be abusive. There are subjective tests for this. Generally doing an image request or some POST data of a few kb isn't going to be an issue. Some ad servers (like sizmek) download 2mb "test images" to exercise their bandwidth from some locations (like the US). - Costs vary based on device, region, the web page the ads are on, and silly things like demographic. Some of these factors are interesting to benchmarkers but others are not. Thinking about what you actually need to test can help keep your costs efficient.