We have been running the Web Stress Tool against our Coldfusion Web Application. We are running the WST from a Client machine on our local network, hitting a test version of one of our web-sites which sits on a server of equal spec as our live boxes.
What we are finding is that whilst both IIS and our Coldfusion System Monitor (Fusion Reactor) are both reporting little or no issues - There seem to be many reported back from the WST. Most of which are 404 errors. During the period the test is running, machines internal and external to our local network have no problem accessing the site - and in most cases there is no evidence of lag.
An example test we have prepared and ran visits two fairly basic pages of the site - with minimal database connectivity when compared to the rest of the site. Here are the parameters for a typical test:-
Test Type: Ramp Run Test for: 20 minutes Number of Users: 200 Click Delay: 5 Seconds Random Click Delay: Checked
What is the most puzzling is that the Avg Time for these pages is typically reported at around 20 seconds - which is not reflected when viewing the site through a regular browser session whilst the test is running.
I can send over example reports of the tests we have been running. Really we would like to determine where along the requests lifespan the error is occurring - as I mentioned earlier everything seems OK under the stress produced by the WST, except the errors that are reported.