Performance Testing Tips

For running the script in  Controller/Performance Center a lways use data file as unique on each iteration in parameter setting. Generally we select parameter file sequential on each iteration which is not a good practice, this option will force all users to pick the first value of parameter list. e.g: if there are 100 users and we have 100 data in parameter file, when we select sequential on each iteration then all the 100 users will pick the first data and then in second iteration they will take the second data. If the data is unique and can be used by only one user at a time then our script will fail. However when we run the same script in VUgen then it will pass. We can use another method to validate the data in VUgen itself rather than running it in Controller. Use blocks in Run Time setting and keep init and end part in action and run it for 100 iteration. In this case on every iteration it will take the new data from parameter file. But this is not a good practice as...

Manual Scenario: In Manual scenario we define the number of Virtual Users that will hit the application, In this scenario we don't bother about the number of hits or throughput e.g, if we want to check the stability of application on the Vuser load of 500, then we can specify the number of Vusers to 500. Goal Oriented Scenario: In this scenario we decide the goal of execution by setting the number of  Hits/sec,  transactions/sec, Number of  Virtual Users, T ransaction response time and P age per minute.  The scenario will run till it achieves the number of hits or the defined parameter. e.g if we set hits=50, the scenario will run until it reaches hits to 50.