Somebody tryes to work with Microsoft Web Application Stress Tool? i need to simulate more than one request from one user and recently downloaded this tool for free but didn't understand how to solve my task.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Serguei: Somebody tryes to work with Microsoft Web Application Stress Tool? i need to simulate more than one request from one user and recently downloaded this tool for free but didn't understand how to solve my task.
From what I understand of the product (have been using it for 2 weeks so someone correct me if I'm wrong!) you go to Settings and increase the value that says 'Stress Level (threads)' to the value you want. If this number is above 50 then you use the multiplier value in 'Stress multiplier(sockets per thread)' to get realistic results for numbers above this.
Responding to the statement about Microsoft using RSW to load test their apps - we are currently employing some Microsoft consultants to work with us and they are using/recommending their own tool (Web Application Stress Tool) so I very much doubt it.
This is for jwood, I did not see an email address. However what I wanted to know is how is it going now (using Microsoft WAST). Why because I do see this as a viable alternative (in some cases) and would greatly reduce the cost of a performance test engagement. send me an email so we can discuss off line.
"Get busy living, or get busy dying." Andy, Shawshank Redemption.
Does anyone know how to set the MS Web App Stress tool to test hitting a page or a sequence of pages once?
Currently I can only set it to run for a certain time period not specify the number of hits. How do you do a specific number of page hits?
Try this: set a delay after the last step in the script of greater than the test duration.
but why would you want to do this? there are better utils on the mkt to do single user download times. and also unless you are testing across a LAN you will get different times each time due to latency. so you result may b good, or bad, but either way unreliable(?)