 |
Overview |
System Requirements |
Screenshots
|
|
Details - Critical Mass - Web Stress and Performance Testing
|
|
|
Goals
1) Simulate web site traffic under a variety of load conditions.
2) Gather data during virtual load.
3) Analyze and report the results.
|
|
Critical Mass provides a browser based script recorder, script editor,
local and remote testing components (for playing back scripts and simulating users),
remote performance monitoring and centralized gathering and reporting of data.
|
|
|
|
Setup
|
|
Using the supplied setup program you install Critical Mass on a PC from where all
web performance testing and reporting will be managed.
|
|
Next (using the supplied setup program) you install remote test components
on additional PC(s). The purpose of the remote test component is to provide
additional virtual users beyond the capacity of a single PC. The number of
remote test modules that may be used is unlimited.
|
|
Last (using the supplied setup program) you install a remote performance monitor
on the web server(s) to be tested. The purpose of the remote performance monitor
is to allow you to specify and gather specific web server performance data from a
centralized location.
|
|
|
|
Using Critical Mass
|
|
First you create a new project. A project groups remote test PC(s),
remote performance monitor, web server being tested, test script, testing instructions,
result data, etc. together so that different testing and analysis can be done over and
over with a minimum of effort when switching between projects.
|
|
In the project properties window you set the number of virtual users for the local PC and
for each remote test PC. You also specify the web site to be tested and the starting page
on that site for testing.
|
|
Once the project properties are set you can use the built-in browser (or optionally a browser
of your choosing). As you access the web site all actions are automatically recorded and
saved in a test script that will later be used by the virtual users to simulate web traffic.
The script can be edited at any time to change recorded actions, add hard or random pauses,
etc.
|
|
Next you specify the performance data to monitor when testing occurs.
|
|
Next you access the Critical Mass Stress Test Window and start testing. Data is
displayed for each local and remote virtual user. As testing occurs information
is displayed for each virtual user: HTTP request and response, status, warning,
KB received, the number of tests completed and location of the virtual user.
|
|
While testing occurs, the remote performance monitor (on the web server being tested),
records all the necessary statistics at one second intervals. When testing is complete
the performance data is automatically sent to the central management PC where it is saved.
This data can be used as the source for a variety of preconfigured and / or customized
analysis reports.
|
| |
|
System Requirements
|
|
The client central manager and remote testing components require Microsoft
Windows 98, 2000 or XP operating systems.
|
|
The remote performance monitor component requires the Microsoft Windows 2000
or 2003 operating systems running IIS.
|
|
TCPIP connectivity is required on all PCs and each remote component requires a
separate (configurable) port be available.
|
|
Internet Explorer (minimum version 5.01 SP2 required, I.E.
version 5.5 or higher recommended) is required on the central management PC
and on the web server.
|
| |
|
Critical Mass Screenshots
|
|
|
Overview |
System Requirements |
Screenshots
|
