This tool only does throughput tests, which are only good for very limited purposes. I am creating a load testing tool at the moment, and I did load test consul

This tool only does throughput tests, which are only good for very limited purposes. I am creating a load testing tool at the moment, and I did load test consulting for a number of years. Generally we would start with a throughput test to establish a ceiling on the pipe's fatness and the webserver's max throughput. That's really just step 1, though. After that is the more important stuff. In a web application, most bottlenecks are at the database and appserver layers as opposed to the webserver. A good load test needs to be fully transactional so you can simulate login/logout, shopping, searching, or whatever real users of your application do. A good load test also needs error detection (content-checking). Without content checking, I've seen demos where a "testing tool" ran, someone unplugged the DB machine, and everything still came up green. From an end-user perspective, a real user would have seen the "data grid" section of the webpage replaced with an error message and the web app was unusable, but the testing tool was happily chugging along, showing green.