|
|
| Visual Demo [Load Test 10] | Visual Demo [Load Test 25] | Visual Demo [Load Test 100] | Visual Demo [Adaptive Playback] | Visual Demo [Java Applet Recording] | Visual Demo [Quick Check] | Visual Demo [Tune] |
Here is an example of the eValid LoadTest feature available with an eValid LOAD License. This particular example runs 100 eValid browsers in parallel using 5 different script files opening each sub-browser as a 50x50-pixel browser instead of a maximized browser -- this is done because, otherwise, the screen area becomes too busy. Each browser is set to repeat running each script 5 to 10 times.
Start by making the script .evs file(s) that are to be played back in parallel. Then make the loadtest control file, evloadtest100.evl, with whatever quantity of browsers and options that satisfy your loadtesting needs.Remember: Make loadtests that utilize your available bandwith on the Internet connection available to you. Don't over-load your Internet connection. Also, remember to keep all necessary files in the path that is set in the Settings > Record/Play Preferences menu, as all sub-browsers use the path that you set through the Preferences menu to the Registry.
Go To Bottom Of ScriptGo To Top Of Script
This test was run on a 733 MHz Pentium III with 512 MBytes of RAM and a 64 MB AGP Video Card. The machine is running Windows 2000 Professional SP 2 and has an IE 6 browser installed. To obtain these results we had to make certain adjustments to some OS parameters: (1) the Desktop Heap was set at 32,768 Bytes (set at intervals of 8,192 Bytes); and (2) the Virtual Memory was set to 900 MBytes. For more information on these machine adjustments, please see the CPU Adjustments page.
Click Playback > Start Playback to begin the playback process. When playback has completed, click Window > Logs > LoadTest Log.
The pictures (with thumbnails) below show: (1) Running this LoadTest script with 100 browsers in parallel (the picture shows only a portion of the screen, which can become extremely busy); (2) The resource utilization when running 100 browsers in parallel; (3) The LoadTest Chart that shows the results of the execution.
This is an excellent way to test the performance of your WebSite and server under heavy load sessions. You can gather data on how well your site performs when many users make requests for your WebPages. One can also see how multiple simultaneous requests are affected by the backbone of the Web, the design of your WebPage(s), and the limitations of the server where your WebSite pages reside.
One can learn that the Web's performance, and your ISP's performance, greatly vary through out the day. The best weapon one has at his or her disposal is to design the WebPage to be efficient as well as effective.
