In part 1, we covered writing web app load tests using multi–mechanize.  This post picks up where the other left off and will discuss how to gather interesting and actionable performance data from a load-test. The big problem we had after writing load tests was that timing data gathered by multi-mechanize is inherently external to the application. This means it can tell us the response times of requests when the app is under load but doesn’t identify bottlenecks or configuration problems. So we need to be gathering a bit more data about how the internals of our web application respond to the workload. Read more here.