Writer: DEMONALEXEMAIL: DEMONALEX_AT_DARK2S.ORG Preface: After reading SQL "DOS attack" with Web pressure test tool simulation, "especially, especially, to find out some of this software, special for this time Experiment (thank you for many netizens for this "to donate your own server), write the next rotten text, I hope to add SQL big brother who has not been aware of knowledge points in this article. Reference: "DOS attack" with Web Pressure Test Test Tool Simulation "," Web Pressure Test Guide "Webstress has always been a number of IDC evaluators, network administrators, and network security experts for server performance Test and evaluation of objects. Today, the little gods have a web pressure test for a webmare for a netizen (suggestion: pressure test is usually arranged after penetration test). Experimental environment: Win2000 Advance Server Iis Fiber Band Width Tester (Client): Win2000 Professional MS Web Application Stress China Telecom ADSL Experimental Purpose: Test and Analyze the HTTP Service provided by the Web Server Comprehensive stability. Test Scheme: Baseline: Static Test Case (HTM, JPG) [Because friends only use simple HTML] test tools: single client, test case library, client program analyzer: adopt comparison analysis test object : Enterprise-level all-round virtual host comparison object: "China Resources" Virtual Host (DARK2S.NET) Test Scenarius Condition Numerical Indicators: *********************** *********************************************************** *********** URL thread duration uses a random delay virtual killing bandwidth other value ------------------------ -------------------------------------------------- -------- Random Traverse Address 20 5 minutes 200-400 (ms) 56K MODEM (44K) Default ********************************* *********************************************************** *********** Experimental steps: Generate two new pressure test scripts using Web Application Stress -> Record its URL-> Configuration Condition Test Description -> Test -> Generate Report-> Introduction to the report, the result is specifically operating: Localhost opens the MS Web Application Stress main program to select: "Scripts" -> "create" -> "record", select "Record Delay BetWeen Request, press "Next". "finish". Next, fill in the web server address you want to test in the address bar of the pop-up browser, randomly browse a few pages, simulate some of the features of the web using the web. Finally close the browser, click the "Stop Recording" button back to the main interface, where you will see a URL behavior list script (including behavior, URL address, group, delay), and finally in the main script The host address that needs to be tested in the "Server" input field above the script display interface. As shown below: After completing the above steps, click "Settings" in the script list to enter the settings display interface and fill in the relevant parameter metrics. Finally, return to the main display interface, click "Run Script" to enter the pressure test state in the toolbar.
Use Active Ports to view their connection, from below the figure, it is not difficult to find that WAS is now using a multithreaded multithreading for the host to simulate connection testing. After the test is complete, click the "Reports" button of the toolbar to view its test report. The test report is distributed in the form of a tree, the root is divided by the test server, the root is the test date, and the branching portion under which is a classification indicator value of various types. We have to get the macro numeric indicator of the entire test server only need to click the test date "Subweight". Use the same steps and parameter indicators as the above test ', such as the remaining server (because of the relationship of time, the little god has previously put it up in advance: P). The last remaining job is the data planning and comparison analysis. At the beginning, I thought it would be necessary to manually do data planning these delicate finishing work (Xiao Shen can be a famous old eye!), And later found that WAS is a built-in database (Microsoft is not a water-free lamp). Using the ancillary tool Access of MS Office to open the WAS.mdb database file in the WAS directory, all test conditions in the project are ranked in front of your data in the 'table'. You only need to find the desired attribute class table and gently, it will be at a glance. Next, this .mdb database is saved, and used as the preliminary data analysis of the test. It is followed by comparison analysis. Simply use Access to open the original. MDB database, and through the 'subtomb' link The comparison of the indicator data can easily perform the comparative analysis of the data class table that needs to be analyzed with the 'Report' class table. Of course, if your boss is particularly needed, you can also make a variety of analytical reports in conjunction with Word, Excel and other tools ... The "things" small gods don't say much. : P. This article is written here, this simple Web pressure test project is considered a paragraph, of course, the Web stress test in real life is not so simple (maybe the Webstress test in real life will make you crazy: P) . Finally, let us summarize the basic steps throughout the test: 1 understand the software used to test. This is the preparation work before the test. Any project should have a comprehensive understanding of it before starting the test. If this software is dry, its function and performance is mainly reflected in what kind of aspects, what is characteristic, How to reflect these features. 2 Demo test plan. The test plan is to define a test project process in order to correctly instantiate and control test. 3 The process of implementing the test. Follow the test plan, under various conditions, run the prior design test script, record the performance parameters of the WE B server and related clients. 4 Analyze the test results. Testing will collected a large amount of data, which can help analyze the performance of the web application based on this data. ######################################################################################################################################################################################################################################################################################################## ######################################################################################################################################################################################################################################################################################################## ############# Some Tips About WAS: After installing WAS, each time Windows starts a service called "WebTool.exe" while Windows (process: "WebTool.exe") Distinguished to "Management Tools" -> Services, adjust this service to "Manual", and stop the service after each use of WAS, so as not to take up your system resources for a long time. ######################################################################################################################################################################################################################################################################################################## ######################################################################################################################################################################################################################################################################################################## ############## 相关 测试 Web Application Stress (WAS) can be downloaded from the home page http://DEMONALEX.DARK2S.ORG.
Appendix: Basic indicator list of web pressure test ========================================= ============================================================================================================================================================================================================= ==== Number of Hits
: Test interval Virtual users click on the total number of times
Requests per second
: Number of requests per second client
Threads
: The number of threads, that is, virtual users and launches
Socket Errors Connect
: Socket error connection
Socket Errors Send
: Socket error delivery
TTFB AVG
: From the first request to the test tool to receive the average time between the first byte of the server response data
TTLB AVG
: From the first request to the test tool to receive the average time between the last byte of the server response data
According to the above data, the application performance can be analyzed from the following aspects to generate the corresponding report.
:
Number of hits vs. users
: As the virtual user increases, the total hits the server can process within the specified time.
Requests per second vs. user
: As the virtual user increases, the server requests the request per second per second in the specified time.
Errors vs. Time
: As the simulated access time continues, the number of errors occur
Errors vs. user
: As the virtual user increases, the number of errors occur
Performance Distribution vs. Users
: For the application performance distribution of virtual users, including the memory of the server, CPU usage, etc.
Performance vs. users
: As the virtual user changes, the performance of the application performance is ====================================== ============================================================================================================================================================================================================= =======
