Glossary

    A
  • An API Vuser emulates a user's actions at the network API level. For example, HTTP requests and responses without rendering the UI.
  • A component of a load test such as a script, server, or topology.
  • D
  • The specified time that the test will run. The duration does not include ramp up and tear down.
  • H
  • HTTP Archive file. The common format for recording HTTP tracing information.
  • L
  • The amount of time that it takes for an IP packet to travel across the network, from the client to the server, or from the server to a client. The actual network latency is the emulated latency plus any latency that exists in the actual network.
  • A test designed to measure an application's behavior under normal and peak conditions.
  • M
  • Entity that you want to monitor during your load test, such as an application or web server.
  • N
  • Collect navigation timing data for each object on a page being loaded by the browser.
  • P
  • The amount of time to wait between script iterations.
  • The percentage of IP packets that are sent through the network, but do not reach their destination.
  • R
  • The rate at which Vusers are started.
  • S
  • The recorded actions of a business process.
  • An entity that you want to monitor during your load test, such as an application or web server.
  • Threshold that a transaction is expected to meet. For example, maximum transaction response time must be less than 3 seconds. If a threshold is not met, the SLA is considered broken.
  • T
  • The rate at which Vusers are stopped.
  • An entity that represents the relationship between the network components of your application.
  • U
  • A UI Vuser emulates actions on the UI level. For example, a user clicking a button. Since the UI has to be rendered for each Vuser, these Vusers consume significantly more processing resources.
  • V
  • A virtual user emulates user actions in your application. Define how many Vusers will perform the business process recorded in your script during the load test.