
It mimics a crowd of users hitting your app at the same time, which is how you actually catch the bottlenecks. Need more load than one machine can generate? Spread the test across several. While it runs, it tracks response times, throughput, and error rates, then charts all of it so you're not reading raw numbers. Review collected by and hosted on G2.com.
Expect a steep learning curve. Basic tests are fine, but once you get into anything advanced you'll need real scripting chops. And the GUI is a resource hog: run a big test through it and things slow to a crawl or just fall over. You're better off running headless or spreading it across machines. Review collected by and hosted on G2.com.