|
|
Vocabulary/Terminology
As part of the regular eValid vocabulary,
we use certain terms in a special way for LoadTest runs, as defined here.
| TERM | Key | DEFINITION | |
| Test Script | G | The *evs file that is used to compose the scenario. | |
| Scenario | L | The *evl file that is running. | |
| Width/Wide | L | Number of simultaneous browsers (number of _eValid commands in *evl file). | |
| Depth/Deep | G | Number of repetitions (parameter in *evl file). | |
| Respawn Interval | L | Number of playbacks to complete before respawning; 0 = never respawn. | |
| Notation | L | We denote an N-wide, M-deep, n-respawn test as an NxM-n test. | |
| Launch Interval | L | Number of msec to wait between eValid launches. | |
| -O Switch | G | Keep browser open after launch (command line switch) is used to study behavior of a resident, quiescent browser at the end of the LoadTest session. | |
| Footprint | L |
How much RAM one eValid browser takes.
Read this value from "Mem Usage" in the Task Manager Display. | |
| Mem Usage | L |
Current working set size that resides in memory.
This will go up and down depending on what the eValid browser is doing.
Figure on about 2-4 MB for a quiescent eValid copy.
Read this value from the Task Manager Display. | |
| Peak Mem Usage | L |
This is the largest amount of memory the eValid browser
has required since it was launched.
Read this value from the Task Manager Display. | |
| RAM = Commit Charge L |
How much RAM all current processes take (including all eValids)
Read this value from the Task Manager Display | ||
| Script Size | G | Number of non-comment lines in the script. | |
| Script URLs | G | Number of URLs referenced in the script. | |
| LAN/WAN | L | Whether the tests are being done entirely on a LAN (where transfer times are very small) or on the WAN (where transfer times can be expected to be larger). |
Key Definitions
L = LoadTest, G = General, F = Functional Test,
R = Regression Test, M = Monitoring, S = Site Analysis
