Veena,
HP bought Mercury, therefore it is now called HP LoadRunner.
We ran several different scenarios of load testing on our EP 7.0 instance before we went live.
One scenario involved running a script in which a user logs into the Portal, accesses the home page, and then logged off. We set that this script should not take no more than 10 seconds to complete. We then ran this scenario with different numbers of concurrent users (5, 10, 50, 100+) until we determined the maximum concurrent usage the EP system would tolerate while staying below the 10 second threshold. This told us if we needed more CPU and/or memory to reach our estimated concurrent usage.
Another scenarios involved running a script in which the user logs in, accesses the home, but does not log off. This is a more accurate behavior as most users close their browser without clicking the logoff link. We ran this script in a step-wise fashion, adding 10 new users every 5 minutes until we reached capacity. This told us our maximum logged-on user count. It also told us if we needed more memory or whether we needed to decrease the session timeout.
We also ran combinations of both, but this did not tell us any more.
- Andrew Castillo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.