LoadRunner Stuff

Do’s:

• After each performance test run, clear the logs for database and application. Large log files may result in inaccurate performance results.
• To mirror the production environment, identify the correct software and hardware for server.

• When a load is being generated on the system; to capture end user response time, use a single GUI client. If you need to generate load by using multiple client computers, you should consolidate data at single client computer / machine and generate results based on the average values.
• During a load test, include a buffer time between the incremental increases of users.
• To create a more realistic load simulation, always Use different data parameters for each simulated user.
• Never overly stress the client. Monitor all systems involved in the test including client that generates the load.
• According to high volume transactions and critical functionalities, prioritize your scenarios.
• If you need to fire concurrent requests, then, to identify bottleneck issues, use think time as zero.
• Do stress testing for critical components of the system to assess their independent thresholds.

Don’ts:

• During load testing, never ever allow test system resources to cross resource threshold limits from a significant margin – Otherwise, it will distorts the data in your results.
• For performance testing, always use an isolated test environment, but that environment should be exact replica of production environment. There should not be any other traffic load.
• Do not put too much stress on the client test systems.