Windows Azure Platform Family of articles Catalog
In the previous section, I explained that before we did the Azure performance test, we first needed to submit the permeability test sheet
Windows Azure Handbook (8) Azure Performance Test (1)
Next, the author will introduce the performance test, the need to pay attention to the problems to introduce:
(1) If possible, put the test machine, and the Web server, in the same intranet for performance testing
This can reduce the negative factors caused by network delay to a minimum
(2) If the test machine is local, the Web server is in the cloud. Consider whether the local network has sufficient upstream bandwidth and whether local network devices have QoS
I've met some developers complaining that there are a lot of failed requests when using a local PC for stress testing. We need to consider the situation of network asymmetry.
I recommend that when the Web app is deployed in the Azure Shanghai Data Center, the test machine can use the Azure Beijing data Center
(3) Set a reasonable page response time
I have encountered performance test metrics, server-side in the Azure Beijing data Center, customer's test server in Guangzhou. The test metric requires 400 concurrent users, and the page response time is 300 milliseconds.
Well, it's really not easy to do.
(4) Use of proven stress testing tools, such as
-Load Runner
-Apache AB
-Apache JMeter
-Visual Studio Test Agent
(5) Special attention is required when using the load balancing rules for destination IP based on azure source IP.
Because more than one client uses the same source IP address, it can cause a single server to be under a lot of stress, so the pressure is not average at this time.
Windows Azure Handbook (9) Azure Performance Test (2)