The High Availability Test Console now has a few more features for you to use! The biggest change is the addition of a server crash test that has been implemented.
Remember: In order to use this feature you must update the High Availability Site Extension. This can be done in one click from either the azure portal or your Kudu site extension.
This new test will simulate what would occur if the server on which your site is hosted was to crash. This test is run the same as the others, you can run them all in a row or you can run this test on its own by clicking the respective play button.
The difference between this test and the CPU and Memory Test is the how to interpret the results. The previous two tests display and expected and an observed value for latency and success rate. In this case we are just interested in finding out how your web site will respond in the case of a server crash. The only metric displayed in this case is seconds downtime. This number represents the amount of time that your site was unable to be requested. Obviously, the shorter the better.
A success is constituted by a downtime of one second or less. If you were to scale your website to even just two instances you would be likely to see that there was no downtime at all. This is because Azure Web Sites will randomly direct the incoming requests to one of the two instances. Even though one instance will be down for a couple seconds in the event of a server crash, half of the requests will still complete.
If high availability is really important to you this is another test that shows how crucial multiple instances or the auto scale features provided by azure can be for your web site.
Another new feature is the ability to view the page in Japanese. This is a feature that will hopefully grow to allow the site to be viewed in multiple different languages. (I am sorry if some of the translations are not accurate)
You will also notice that there are two more text boxes in the authorization pop up. The first will show the web site URL that you just entered. If for some reason the web site does not appear to be a valid Azure Web Site, an error message will be displayed and you should double check the URL. There is also a place for you to enter your email address. This will be used to send a report of the test results to your email address. Right now, you may be contacted to provide feedback on the product if you supply your email. This is a way for you to help shape this tool into something that you can really use to help make your site better!
Finally at the bottom of the page you will see that there are links to this blog as well as to the Azure home page and the web site source on git hub.
Expect another release, post, and even a video at some point this week!
No comments:
Post a Comment