Guest daxu Report post Posted April 20, 2011 Hi, I am new to this tool, so maybe my test method is not correct. On one machine, I simulates 300 users accessing two javascript files on my IIS web site on development server. The think time is from 0 to 1. Profile1.page_1 Min 0.03 0.05 0.1 0 0.007 0.1 0.08 0.12 0.14 0.13 Avg 0.97 0.79 0.73 0.82 0.78 0.73 0.74 0.77 0.81 0.84 Avg90 3.08 2.53 1.83 2.16 2.38 1.93 1.78 1.66 1.69 2.12 Max 19.1 35.9 12.1 15.3 16.9 32.7 16.7 7.9 10.9 26.7 Profile1. Min 0.09 0.24 0.49 0.02 0.04 0.37 0.34 0.46 0.57 0.53 Avg 1.4 2.09 2.29 1.77 1.86 2.14 2.19 2.4 2.45 2.53 Avg90 3.07 4.72 5.13 4.22 4.99 4.64 6.09 4.81 5.1 5.24 Max 19.2 32.0 36.0 37.1 35.5 54.1 83.0 27.4 47.5 32.7 HTTP reply codes Code Request Number Profile1 - 30,175 200 OK Profile1.All 30,082 200 OK Profile1.page_1 (1) 15,097 Profile1. (2) 14,985 Timeout Profile1.page_1 (1) 27 Profile1. (2) 10 Network error Profile1.page_1 (1) 38 Profile1. (2) 18 I can see that the avg90 is ok, but the max is going to 26 seconds or 32 seconds. The thing is that I have IIS trace on for everything longer than 5 seconds to finish and I don't see anything logged there. So for the Max entries, are they successful ones (with 200) or they are the timeout or network error ones? Many Thanks Quote Share this post Link to post Share on other sites
sergei 0 Report post Posted April 21, 2011 WAPT takes into statistics successful requests only. But WAPT itself can impact on statistics if it was overloaded. Quote Share this post Link to post Share on other sites