Beruflich Dokumente
Kultur Dokumente
0 Introduction
1.2 Objectives
. To develop a
1.3 Scope
4.1 Creating and Publishing the Container Management System Web Application using Azure
When the researcher has created the Container Management System web application, the
researcher will start publishing to the Azure. Firstly, the researcher will create a new resource
group that focus in the Southeast Asia legion in the Microsoft Azure Cloud to host the
Container Management System web application and Southeast Asia SQL. There are few
procedures will be showing how to host the web application.
There are few requirements need to be enter which are the name of App Service Plan,
Subscription, Resource Group, Operating system, Location and Pricing Tier. The advantage of
using this, it can help to save budget on hosting various of application by configuring the web
apps to reuse a single app service plan.
Figure 2: Create an App Service Plan for Container Management System
3. Create Web App Service plan for the Container Management System
There are few requirements need to include which are App name, Subscription, Resources
Group, OS, Publish, App Service plan/Location and Application Insights.
In Unit Testing, the researcher will be focused on the small section of the system web app code.
Therefore, to make sure that the small part of section will not be affected the other part. If not,
the system will not be working well. It can cause the researcher spending more time on redo
the code part of the system.
The researcher will conduct two performance testing for the same web application. One is free
version with limited number of user and quota to test. Another one is paid version with
unlimited of quota and users to test. In this performance testing, the researcher will perform
testing with two different requirements of testing which are 1000 user with 10 minutes and
3000 users with 10 minutes.
As shown in figure x, the researcher needs to link the web application to the web app then only
can start running the performance testing. However, the researcher is required to fill in the
testing requirements which are the name of experimentation, the number of users to load, the
duration of testing and load from where. In the performance testing, the user will set-up two
different of requirements which are 1000 users for 10 minutes and 3000 users for 10 minutes.
After the performance testing is completed, it will generate a report of the performance testing.
The table above shows the results of load testing before scaling up. The researcher uses the free
version of the load test. There is a limitation for the free version of the load test which is a
limited number of users and a limited number of quota. The average of the response time in the
PerfTest01 was 0.01 seconds. However, if the users set up to 3000, the average of the response
time was 0.32 seconds. The success rate in the PerfTest01 and PerfTest02 which are 3602
(0.6%) and 70226 (4.26%). The failed request rate in the PerfTest01 and PerfTest02 which are
601424 (99.4%) and 1577296 (95.74%). Significantly, due to the free version of the load test
of the functionalities. Besides, the request per second for two different testing which are
PerfTest01 is 10008.38 and PerfTest02 is 2678.9.
The table above shows the results of load testing after scaling up. The outcome of the load
testing is better than the free version of the load testing because of the paid version of the load
test has provided an unlimited number of users and quota to test. For example, the successful
request rate in the paid version of the two load tests was 136614 (97.64%) for the PerfTest03
and 146190 (96.55%) for the PerfTest02. If the company want to test their web application is
better to scaling up, this can help them to identify around the world able to use without any
issues when other countries want to use.
As shown in figure x, the application insights scale up to the paid version. The researcher has
performed the availability testing for seven days. The testing result has the high success rate
compared to the unpaid version of the availability testing. If the web application is focused on
the worldwide, it requires to have an unlimited number of quota for the azure to test is the web
application can work well in real life by examining through the Azure virtual. The average test
duration is 992ms, and the total of the successful test is 14,000, and the failed test is zero.
However, the researcher has configured a few locations to test the web application which are
Japan East, North Europe, South Central US, Southeast Asia, UK South, UK West and West
Europe. Therefore, to check any location having an issue with connect the web application.
6.4.1 Login
6.4.2 Sign up