In this Blog, i am trying to clear some basic queries and as well helping to provide some basic information. This may help you in when you are just starting to learn this tool or while preparing yourself for some exams.
Recording Option - HTML based or URL based
HTML based scripting:
It records script from every user action that is performed during recording.
It does recording as you perform clicks and doesn't give you inside information like what is happening behind the recording.
It is smaller and is more intuitive to read as the statements are inside the functions corresponding to the user action performed.
It is recommended for browser application.
The advantages of using the HTML recording mode is that the size is very compact and the customization efforts reduced.
However, with UI changes to the web applications the scripts would require much higher maintenance costs.
URL based scripting:
It records each and every browser requests to the server and resources received from the server.
It records each and every step and emulate Javascript code.
In this mode all the statements gets recorded into the web_url().
It is recommended for thick client application.
LoadRunner does server side testing.
Transaction Percentile in Loadrunner result
In summary report of Loadrunner result, you might have seen 90 percentile column.
This is usually to check if we have met SLA. We can similarly have other percentile value as well. By default, LoadRunner provides 90 percentile result.
We can change the percentile result as per our need. Click on 'View' in Menu bar. Then Click on summary Filter. A dialog box will open and you will Additional Setting. There you can change the Transaction Percentile value from 90 to whatever you need. Usually, the client requirement is to check 90,95,98 or 99 percentile.
The question is what is this percentile and how do we calculate them manually. In order to calculate the 90 percentile response time for a transaction, sort all the response time values for that transaction in ascending order. Take the first 90 % transactions out of this set. The response time that has the maximum value in this set is the 90 percentile value of the studied transaction. In other words maximum response time for best 90 percentage of the transactions.
Types of Scenario
When we launch controller, we are asked to select the type of scenario that we want during our load test. We have two options for it - Manual or Goal Oriented. Let see them brief...
Manual scenario:
When you choose manual scenario you create it by selecting scripts to run, providing load generators on which we need to run the scripts, and distributing Vusers to run among the scripts. We provide all these details manually and hence the name.
We also have to provide details for Vuser that how we want to distribute them. We have two mode again - Quantity wise or percentage.
Vuser group mode - In this, for each script you assign a number of Vusers. You can instruct all Vusers in a group to run the same script on the same load generator, or you can assign different scripts and load generators to the various Vusers in a group.
Percentage mode - In this, you define a total number of Vusers to be used in the scenario, and assign load generators and a percentage of the total number of Vusers to each script.
Goal-Oriented Scenarios:
In this scenario, you define the goals you want to achieve and LoadRunner automatically creates a scenario for us based on these goals. We usually define our goal based on below types of goals.
Types of Goals:
Virtual Users - This goal tests if your application can run a specified number of Vusers simultaneously. Running this type of goal-oriented scenario is similar to running a manual scenario.
Pages per Minute/Hits per Second/Transactions per Second - These goals test the strength of your server. For each of these goal types, you specify a minimum-maximum range of Vusers for the scenario to run, and in the case of the Transactions per Second goal type, you also specify a transaction name.
Transaction Response Time - This goal tests how many Vusers can be run simultaneously without exceeding a desired transaction response time.
Run as thread or Process
Loadrunner provides as option of Multi-threading. We have two ways to run it - Run Vuser as a thread or Run Vuser as a Process.
When we run Vuser as a process, LoadRunner creates one process called mmdrv.exe per Vuser. So if we have 10 Vusers running, we will have 10 mmdrv.exe processes on our machines.
While when we run Vuser as a thread, LoadRunner creates 1 thread per Vuser. So if we have 10 Vusers, then we will have 1 process with 10 threads running inside it if the limit is 10 threads per process.
Thus from the memory point of view while running a load test, running Vuser as a thread is more memory efficient that running Vuser as a process for obvious reasons that less memory resources are utilized when we run them as thread.
Types of Parameter
We have below list of parameter types when we do parameterization while enhancing our recorded scripts.
Custom
Date/Time
File
Group Name
Iteration Number
Load Generator Name
Random Number
Unique Number
User defined functions
XML
Vuser ID
No comments:
Post a Comment