Stress testing and performance analysis tools

Here we use Microsoft Web application stress tool for web stress testing, Microsoft Web
Application stress Tool
Developed by Microsoft's website testers, it is a set of tools specifically used for actual website stress testing. With this powerful stress testing tool, you can use a small number of client computers to simulate a large number of users.

Before the website is launched, test the website you designed in a real environment to identify potential system problems, further adjustments and setup of the system
. These features enable the DOS bombing function.

1. Simple tool settings

Open the web application stress tool. A simple page is displayed on the toolbar, with function options in the lower left and detailed setting options in the lower right. Before stress testing the target Web server, make necessary settings.

　
(1). In the "Settings" function settings (for example), one is the stress level.
(Threads) It specifies the number of threads used by the program in the background for requests, that is, the number of connected clients to be simulated. What is more vivid is to set the number of bombing threads. Generally
500 ~ 1000, because the number of threads is set based on the local capacity. If you have sufficient confidence in your machine configuration, the higher the setting, the better the bombing effect.

(2) In "test run time", specify the duration of a stress test, which can be divided into days, hours, minutes, And seconds. Set the duration based on your actual situation! Set the test time to 1 minute.

(3) You can set other options based on your own situation.

2. Stress Testing

Step 1: Right-click the tool and select the Add command to add a new test project: memcache, set it, and enter the server to be tested in the main option
IP address. Here we are testing on the local machine, so enter localhost. Select the Web connection method to be tested at the bottom. Select the mode verb here.
Get and Path: select the path of the web page to be tested. Enter/webmemcache/memcache. aspx, that is, the memcache. aspx that is added to the cache.
Page (for example ).

Step 2: set the number of stress level (threads) threads to 500 in the "Settings" function settings. After that, click the gray triangle button in the tool to perform the test (for example ).

Similarly, we have created a nomemcach project to test the nomemcache. ASPX page. After testing memcach and nomemcach, click reports on the toolbar to view the test report:

3. Performance Analysis

Test report of memcache. aspx:

Overview

========================================================== ==========================================================

Report Name: 2009-7-20 10:52:00

Run on: 2009-7-20 10:52:00

Run Length: 00:01:12

Web application stress tool Version: 1.1.293.1

Number of test clients: 1

Number of hits: 2696

Requests per second: 44.93

Socket statistics

--------------------------------------------------------------------------------

Socket connects: 3169

Total Bytes Sent (in KB): 646.80

Bytes Sent rate (in kb/s): 10.78

Total Bytes Recv (in KB): 2019.37

Bytes Recv rate (in kb/s): 33.65

Socket errors

--------------------------------------------------------------------------------

Connect: 0

Send: 0

Recv: 0

Timeouts: 0

RDS results

--------------------------------------------------------------------------------

Successful queries: 0

Page summary

Page hits ttfb avg ttlb avg auth Query

========================================================== ==========================================================

GET/webmemcache/memcache. aspx 2696 1.94 1.95 No

Nomemcache. aspx test report:

Overview

========================================================== ==========================================================

Report Name: 2009-7-20 10:54:01

Run on: 2009-7-20 10:54:01

Run Length: 00:01:12

Web application stress tool Version: 1.1.293.1

Number of test clients: 1

Number of hits: 2577

Requests per second: 42.95

Socket statistics

--------------------------------------------------------------------------------

Socket connects: 2860

Total Bytes Sent (in KB): 589.32

Bytes Sent rate (in kb/s): 9.82

Total Bytes Recv (in KB): 1932.75

Bytes Recv rate (in kb/s): 32.21

Socket errors

--------------------------------------------------------------------------------

Connect: 0

Send: 0

Recv: 0

Timeouts: 0

RDS results

--------------------------------------------------------------------------------

Successful queries: 0

Page summary

Page hits ttfb avg ttlb avg auth Query

========================================================== ==========================================================

GET/webmemcache/nomemcache. aspx 2577 4.75 4.79 No

　
From the test report, we can see that the memcache. ASPX page has 2696 hits in one minute, and the average ttfb is (total time to first ).
Byte) 1.94, average TTLB (total time to last
Byte) is 1.95. These parameters are lower than nomemcache. aspx. In addition, the requests per of memcache. aspx
Second (number of requests per second) is
44.93 higher than 42. 95 on the nomemcache. ASPX page. All these parameters indicate that the execution performance of the memcache. ASPX page is higher
Nomemcache. ASPX page. Cache plays a role in improving performance. Of course, the test I conducted here only simulates the impact of 500 users accessing the web server in one minute
.