登录压力测试

这两天做压力测试，发现无论怎么压，CPU就是上不去

 

测试工具使用siege

服务器分别使用weblogic和tomcat，具体瓶颈点还没有找到，但发现weblogic和tomcat在处理并发上面还是有差异的。

 

 

虽然总的完成时间是差不多的，但响应时间差别很大

 

weblogic响应时间分布

HTTP/1.1 200   5.83 secs:
HTTP/1.1 200   6.12 secs:
HTTP/1.1 200   6.13 secs:
HTTP/1.1 200   5.83 secs:
HTTP/1.1 200   6.27 secs:
HTTP/1.1 200   5.73 secs:
HTTP/1.1 200   6.90 secs:

 

tomcat 响应时间分布

HTTP/1.1 200  17.67 secs:
HTTP/1.1 200  17.57 secs:
HTTP/1.1 200   0.41 secs:
HTTP/1.1 200  18.91 secs:
HTTP/1.1 200   0.37 secs:
HTTP/1.1 200   0.51 secs:
HTTP/1.1 200   0.31 secs:
HTTP/1.1 200  19.20 secs:
HTTP/1.1 200   0.29 secs:
HTTP/1.1 200  19.27 secs:
HTTP/1.1 200   0.30 secs:  

 

是不是能说明weblogic对每个线程的利用比较平均。

 

 

	weblogic 9.2自适应	Tomcat5.5 Maxthread 200 minThread 100
siege -b -c 100 -r 10 -f login.txt	Transactions:                    968 hits Availability:                  96.80 % Elapsed time:                  73.98 secs Data transferred:               0.40 MB Response time:                  5.55 secs Transaction rate:              13.08 trans/sec Throughput:                     0.01 MB/sec Concurrency:                   72.58 Successful transactions:         968 Failed transactions:              32 Longest transaction:            20.07 Shortest transaction:           0.21	Transactions:                    932 hits Availability:                  93.20 % Elapsed time:                  72.36 secs Data transferred:               0.39 MB Response time:                  1.90 secs Transaction rate:              12.88 trans/sec Throughput:                     0.01 MB/sec Concurrency:                   24.53 Successful transactions:         932 Failed transactions:              68 Longest transaction:           29.33 Shortest transaction:           0.09