Microsoft Application Center Test is a test tool that comes with VS.NET. Use it to collect performance information. Determine the capacity of the web application. You can also create a test, simulate multiple users from the web application. These simulation tests It helps to determine the stability of the application. Speed and response ability. We use two examples to see different implementations. The first example is relatively simple. The purpose is to test string objects to use " " connectivity and The difference between the string connection operation using the StringBuilder's Append method. The final result is the same. That is to produce a string of 10000 A. This is the code file name using the operator: StringPlus.aspxprivate void Button1_click (Object Sender, System.eventargs e) {string s = string.empty; for (int i = 0; i <10000; i ) s = "a";
This.tostring ();} The following is the code file name using the append method: stringappend.aspxprivate void button1_click (object reprender, system.eventargs e) {StringBuilder s = new stringbuilder (); for (int i) = 0; I <10000; i ) S.Append ("a");
THIS.Label1.text = S.toString ();
Everyone can see. The above is two different implementations of the same results. After the code is written, we test the performance gap with Microsoft Application Center Test. Open "Visual Studio .Netàvisual Studio .NET Enterprise Edition Features àmicrosoft Application Center Test "Start application. Right click on the" Test "project. New project à Record project start recording the input URL. Record the operation of the item to be tested. Then press Stop Recording. For this test item, you will have a name. Save. A test item creation. Select a test project point to start the test button. That is, the test is started. The following is the result of the test.
The result of approximately 14.5 BPS (BPS-average average request number) with the same method to test the result of the file StringAppend.aspx using the Append method.
Performance is approximately 170 bps (BPS - average number of requests per second)
It can be seen that the string connection is more efficient than using the Append method than using the " " operator. (12 times the efficiency of using the Append method in this example)
The second example is about COM COM only uses .com while providing transaction processing, queue and other advanced performance. In this example I tested using COM and did not use COM environment. The efficiency of the application .Web page program is the same. The difference is the component. The code that does not use the COM is the following code .Namespace Plentysoft.naola.ComplusComponent2 {///
Return "Demo1's I, Demo2's Value IS" SR;}}} Using COM code is just more: ServicedComponent has been tested. Do not use COM test results
Performance is approximately 337 bps (BPS - average number of requests per second) After using COM . The result of the application test is
Performance is approximately 245 bps (BPS - average number of requests per second)
It can also be said that COM can increase 50% performance. But in our ERP application. The COM environment that includes the report is used. This is not necessary. It can be improved.
The above two examples are just two small examples of the Microsoft Application Center Test application. It means that they are only throwing the jade. Let everyone use this tool. Make a better performance application.
