Step 1 - Identify Objectives The purpose of this step is to identify and write the performance objectives of your application. The key question you should ask yourself is: “How should my application behave under load?” The main parameters we should consider are: Response time- The time that would take the application to display a certain output or perform a certain calculation. Example: the product catalog must be displayed in less than 3 seconds. Throughput– The rate of successful message delivery over a communication channel. Example: the system must support 100 requests per second. Resource utilization- A frequently overlooked aspect,

1) Do not use the Console to create your load: You can use the console for debugging purposes or to run a small load from it to make sure the script is running correctly. The GUI consumes a lot of memory under heavy load; therefore the console server by itself cannot sustain a heavy load. 2) Use the remote servers to create the load: Use the “Remote Start All” or “Remote Start” individual servers. 3) Limit the number of threads per engine to 300: This means the total number of threads generated by your test plan should be less than

Performance Testing Process Below is a generic performance testing process 1. Identify your testing environment i.Know your physical test environment, production environment and what testing tools are available. ii. Understand details of the hardware, software and network configurations used during testing before you begin the testing process. That will help testers create more efficient tests. It will also help identify possible challenges that testers may encounter during the performance testing procedures. 2. Identify the performance acceptance criteria – i. This includes goals and constraints for throughput, response times and resource allocation. ii. It is also necessary to identify project success