Load Testing – Version 2012.1.411 (Standalone only)
Telerik’s Test Studio Load Testing enables you to assess how your web applications meet business needs for availability and user satisfaction. We make it easy for you to get started and find the data you need to help make your decisions, but we also give you the flexibility and power to create elaborate, complex load scenarios to meet your most demanding needs.
We’ll help you answer some of the most critical questions organizations have about how their systems behave under load:
- How is a user’s experience on our site when thousands of other users are hitting it at the same time? (General load testing)
- How stable is our site when lots of users have been hitting it for days? (Soak testing)
- How many users can our site support before it crashes? (Stress or tipping testing)
CAUTION: To perform any sort of load testing you must be in control of the website/webserver you plan to test and be prepared for the consequences that may occur as a result of running a load test. It is easy to take down a website using load testing. In fact, that's one of the purposes of load testing: to discover the breaking point of your website. Telerik Test Studio's Load Testing feature has deliberately blocked Telerik.com from being used in a load test for this very reason.
Telerik’s Test Studio Load Testing feature is a set of services and tests that,
when used together, will put your website under a set user load. The user
load is defined by the specific load test being run. Using Test Studio Load
Testing you can measure how your website performs when put under load. Test
Studio Load Testing can measure these properties during the load test run:
| Average Response Time | Over the life of the test, the
average of how long each user response took to be received. Time is
measured from when the request was sent to when the end of the response
was received. |
| Current Virtual Users | The number of active virtual users
at the time a load measurement was taken. |
| HTTP Errors Per Second | The number of HTTP errors received
across all virtual users per second. The load test agent counts HTTP
status codes between 400 and 599 as errors and any general unhandled
exception while making the HTTP request to the web server, e.g. the HTTP
connection was closed, as an error. |
| Total Completed Virtual Users | The total count of all virtual
users over the life of the test that completed all of their requests
without HTTP errors. |
| Total Created Virtual Users | The total count of all virtual
users over the life of the test that were created. |
| Total Errors | Total count of all the HTTP errors
generated or detected across all virtual users over the life of the test. |
| Total Faulted Virtual Users | The total count of all virtual
users over the life of the test that experienced any TCP/IP send or
receive errors during their
run of the test. |
| Total Kilobytes Received | The total number of kilobytes
received across all virtual users. Only the information in the body of
the response is counted. Header information is not counted. |
| Total Kilobytes Sent | The total number of kilobytes sent
across all virtual users of the test. Only information in the body of
the request is counted. Header information is not counted. |
| Total Requests Sent | The total number of requests sent
by all virtual users during the test. |
| Total Responses received | The total number of responses
received back from the server under test by all virtual users over the
life of the test. |
| Total Time On Wire | The total cumulative time (in
seconds) across
all virtual users from the moment each request was sent to the moment
the header for the corresponding response's header was received. |
| Total Time To First Byte | Total time (in seconds) across all virtual
users from the moment a request was sent to the moment the response's
header was received. |
Test Studio Load Testing consists of the following major components and services:
| Test Studio IDE | This is where you create your load
tests and initiate their execution. |
| Load Controller | Test Studio talks to the Load
Controller to initiate and manage the execution of a load test. |
| Load Agent | The Load Agent is what presents
the actual user load to your website by generating artificial user
traffic as defined by the traffic pattern of the load test. You can have
multiple Load Agents being controlled by the Load Controller in order to
create as large of a load as desired. Depending on the specific load
test and the machine's hardware capabilities, a single Load Agent can
represent a few hundred or a few thousand users. |
| Results Database | This is a SQL database where the
statistics gathered during a load test are stored. |
| Load Reporter | The Load Reporter gathers the
statistics reported by the Load Agents and logs them into the Results
Database. Test Studio also communicates with the Load Reporter to retrieve these
statistics for display. Each component can be run on a separate machine or
you can put multiple components onto the same machine. For example, you may want to
put the Results Database and the Load Reporter onto the same machine in order
to reduce the total number of machines required in your load test
environment. |
Learn how to configure these services here.