The team over at OakLeaf posted another summary of some
load testing they are doing with LoadStorm. Apparently, their first round concluded that:

"These tests were sufficiently promising to warrant instrumenting the project with Windows Azure Diagnostics."

The blog post is entitled, "Adding Trace, Event, Counter and Error Logging to the OakLeaf Systems Azure Table Services Sample Project" written by Roger Jennings. It shows how they set up their test scenarios to take actions such as counting customers, creating new customers, and deleting customers. The test run was for 10 to 25 concurrent users over 10 minutes. Roger shares screen shots of everything and shows the load test graphs with increasing traffic as well as a couple of spikes in the error rate. He also digs into the downloaded raw CSV file to find a 500 server error.

Then he shares the code he added to the SampleWebCloudService.sln project to establish Windows Azure Diagnostics. There are several code snippets where Roger illustrates how to make sure configuration files correctly enable the Azure diagnostics, as well as allow tracing and tracking of failed IIS requests.

There is a piece of software to view logs in Azure, and Cerebrata Software Pvt. Ltd. offers a 30 day free trial of its Azure Diagnostics Manager. From the screen shots, it looks like this load test only pushed their processor to small levels of consumption; however, there are enough 500 errors in the log to be a concern.

Very nice blog post. Roger has me curious, and I look forward to the next installment.