In the Beta release there are two available tests, CPU Burn and Memory Test.
CPU Burn
The CPU is obviously one of the most important parts of the hardware supporting your web site. If your site only has one instance, and experiences very high traffic, users could experience the results shown by this test. This test basically starts multiple threads on the hosting VM to continuously perform mathematical operations that will take up a significant amount of time in the CPU. The results of this test can show how your web site performs under that stress. Try changing the number of instances of your web site and see if the results change!
Memory Test
This test is meant to simulate what would happen if most of the memory was allocated and only a small amount was available to your site while experiencing web traffic. You want to build your site in a way that even if memory was to crash and you lost all the information your site was currently using, that it would still be able to recover and resume standard functionality.
The Results
The results consist of three parts, a graph, a table showing expected and observed values, and an explanation in English. The graph and the table both show two measurement metrics, Latency of the HTTP request, and the HTTP request success rate. The success rate is measured on a second by second basis. The graph plots the test over one minute, with the test running for from 20 until 40 seconds, as can clearly be seen above. The values in the table are calculated by taking an average during the time that there was no fault injected as expected and the average during the fault as observed.
The paragraph following attempts to explain the results of the test in a way that helps you improve your web site. This is still the beta version and the hope is to roll out more tests as well as test metrics so each site owner has the ability to build his site to support the highest possible availability.
No comments:
Post a Comment