Your e-Business Quality Partner eValid™ -- Automated Web Quality Solution
Browser-Based, Client-Side, Functional Testing & Validation,
Load & Performance Tuning, Page Timing, Website Analysis,
and Rich Internet Application Monitoring.

LoadTest Detailed Summary
eValid Home

eValid can run a LoadTest scenario made up of repeated playbacks of multiple script files at varying delay multiplier values. Each script file is executed in eValid sub-browsers launched from the top eValid browser, according to instructions contained in a single mast script file -- the scenario file. Varying levels of Playback Fidelity are available, depending on the options you select.

Important Facts
Here are some important facts about the LoadTest capability of eValid:

Shown below is a sample master LoadTest script that invokes the eValid LoadTest engine. The scenario refers to a total of 6 different pre-recorded script files that will be run independently of each other in 10 parallel executing sub-browsers, with each script run a total of between 40 and 1200 times according to the indicated repetition counts and delay multipliers. The assumption is that each of these script files exercises features on the WebSite of interest.

    #  Sample scenario script for eValid V9

    ProjectID "Test"
    GroupID "Load"
    TestID "Scenario_01"
    LogID "Default"

    _eValid "script1.evs"  "Simplest"       60    "$LOGIN=jones $PASSWD=bill"   "-pm 0.9"
    _eValid "script2.evs"  "Not So Simple"  90    "$ACCT=Smith $PASSWD=Any"     ""
    _eValid "script3.evs"  "Type A User"    50    "$USERID=Andrew"              ""
    _eValid "script3.evs"  "Fast Type A"    1200  "$USERID=Jane"                "-pm 0.5"  
    _eValid "script3.evs"  "Type A User"    80    "$USERID=Eddy"                ""

    _eValid "script3.evs"  "Slow Type A"    40    ""                            "-pm 2.25"
    _eValid "script4.evs"  "Type B User"    70    ""                            "-pm 1.0" 
    _eValid "script5.evs"  "Type C Buyer"   100   "$ACCT=smith"                 "-pm 1.0"
    _eValid "script5.evs"  "Type C Buyer"   150   "$ACCT=jones"                 "-pm 0.2"
    _eValid "script6.evs"  "Background"     300   ""                            ""

Master Script Parameter Definitions
Each line in the above script launches one eValid sub-browser and specifies (in order):

In example loading scenario above:

Additional Notes Please keep in mind the following additional factors.

How Many Parallel Copies of eValid Can Be Running At One Time?
These are estimates for the total number of parallel executing eValid browser sessions as a function of typical machine capacity.

With a large number of simultaneous playback sessions the connection between the driver machine and the Web may saturate, thus slowing down all playbacks. Even though running slower, all launched sub-browsers will complete execution eventually -- unless interrupted. However, on a 10 Mbps LAN [or faster] for an IntraNet test, or with a T1 or T3 connection [or faster] for a live test, this may not be an issue.

If a typical user session lasts 10 minutes including "think time", but takes only one minute of actual playback time when the playback delay multiplier is set to 0.0, we say that the duty cycle for that test is 10%. This is a fairly common value for test duty cycles. This means that, as shown below, full-rate (delay multiplier = 0.0) playback of tests can simulate the load imposed by a large number of users. You may need to make some adjustments to system parameters to achieve the below stated performances.

Estimated Playback Capacity on Various Types of PCs
Type2.53 GHz
SmallCore 2 DuoPentium-IV Desktop3GB500
Large 2 CoresEC2 - m1.large7.5GB1000
Huge 8 CoresEC2 - m2.4xlarge68.4GB5000

Machine Details
There are very subtle interactions that affect the level of performance achieved with eValid when used in this mode. Factors such as the available RAM space, the Desktop Heap Space, Virtual Memory Size, and other machine settings affect the level of results achieved. (See CPU Settings for more details.)

In addition, the duty cycle of the running scripts, the speed of the LAN or Web access available, and certain internal characteristics of the machine being used also affect achieved load generation capacity.