Performance testing tools are only testing means, not a period to grasp the many and all, the key is to be handy. Of course, learning more about test tools can be handy and quickly get into the test. The most important thing is to understand the characteristics of the tool, the appropriate test scenario, how high the concurrency needs to be met, what protocols are supported, and whether there is sufficient extensibility.
I'm just trying to sort things out a long time ago. A brief description of the following Web performance testing tools. Because these lightweight test tools do not typically simulate more complex scenarios, there is no performance comparison of the tools themselves.
Http_load:
Download |
http://www.acme.com/software/http_load/ |
Run as |
1. Http_load-parallel 10- Fetches Urls.txt 2. Http_load-rate 5-seconds Urls.txt can be abbreviated as: 1. http_load-p 10-f + urls.txt 2. Http_load-r 5-s urls.txt Parameter introduction -p number of concurrent access processes Span lang= "en-us" > -f Total number of accesses -r per second access frequency, limit greater than 1 less than 1000 -s Total access time Common parameter combinations: -p–f; -r-s urls.txt is the name of the URL you want to access, which can be either a single URL or a file containing a URL. |
concurrency mode |
Http_load runs in parallel multiplexing, unlike most stress test tools, which can run in a single process. This should be the http_load cannot support the high concurrency of the mishap. Reference:http://www.51testing.com/?uid-159438-action-viewspace-itemid-154740 |
Support Agreement |
Support HTTP,HTTPS protocol, the request mode by default is get mode. Post mode is not supported . There are peers to modify its source code can support the post method, Reference:http://www.51testing.com/?uid-159438-action-viewspace-itemid-153701 |
URL parameters |
You can specify a single URL or multiple URLs to be passed as a text file. URL limit: not explicitly limited, but Http_load will read all the URLs into memory, and there is a limit to the size of the file. In addition,too many URLs have a large impact on performance, so it is not recommended to have too many URLs. Reference:http://www.51testing.com/?uid-159438-action-viewspace-itemid-151584 Http://www.cnblogs.com/subsir/articles/2574905.html |
Parameter read mode |
The http_load takes a random read URL. Sequential reads are not supported. Reference:http://www.51testing.com/?uid-159438-action-viewspace-itemid-151584 |
HTTP parameters |
If you need to set the header and body of HTTP , I am afraid http_load is not supported, do not see the relevant parameters to support |
HTTP response Parsing |
The response to the HTTP request resolves the return code, the user cannot customize the parse response, and the write file store is not supported |
Test results |
[Email protected]:~/linsa/http_load-12mar2006$./http_load-r 1000-s 5 Url.txt 4331 fetches, max parallel, 3.36822e+07 bytes, in 5.00107 seconds 7777 mean Bytes/connection 866.015 fetches/sec, 6.735e+06 bytes/sec msecs/connect:4.9993 mean, 3004.15 max, 2.074 min msecs/first-response:2.34363 mean, 207.503 max, 2.119 min HTTP Response Codes: Code 200--4331 Fetches Run the4,331 requests, the maximum number of concurrent processes is15, the total transferred data is3.36822e+07 bytes, the running time is5.00107 seconds Focus: Total number of requests, maximum concurrent processes 7777 mean bytes/connection: each request/Connection transmitted data volume 866.015 fetches/sec, 6.735e+06 bytes/sec Fetches/sec requests per second Span lang= "en-us" >/visits, bytes/sec The amount of data transferred per second Concerns: Number of response requests per second msecs/connect:4.9993 mean, 3004.15 max, 2.074 min Average response time, maximum response time, Minimum response time HTTP response Codes: Code 200--4331 Request Response Code Server return status code: 200-Indicates the request was successful. 3xx--Redirect class 403, 404-Client Error Class (server not found with request uri matching resources. ) 500-Server error class (internal server error) et cetera ... Concerns: Are there 403, 404, 500 error generation |
"Turn" http_load pressure test