This is application/context dependent. Ebay users may have a wait time of 2-20 seconds, where the low end results from scanning a page and dismissing it out of hand and the high end is the result of an auction with a REALLY long/detailed/funny description. Other web applications may have incredibly complex pages that result in a user parking on that page for 60-6000 seconds.
What I suggest is that you convene a group of representative users (could be internal analysts and/or QA members) and record their use sessions. A little statstical analysis on the wait times should provide you with enough data to confidently randomize wait times.
Dennis
| "Nicolas De Loof"
<[EMAIL PROTECTED]>
06/23/2004 08:56 AM
|
|
Hi all,
I've to make some load tests on my app.
Our customer wants the appli to handle "300 simultaneous users". To translate this requirement into request per second,
how many time do you consider an 'active web user' to wait between 2 request ?
Nico.
Our name has changed. Please update your address book to the following format: "[EMAIL PROTECTED]".
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
