Performance Center : Architecture overview

High Level Overview

Loadrunner has the following high level conceptual components:

  1. Injector(s) – Used to replicate virtual users
  2. Controller – Used to coordinate the actions of the simulated users
  3. Realtime monitors – gives information on hardware and software metric’s during simulation
  4. Analysis Database – stores information for post analysis

Any commercial load-testing tool should consist of these.


Communication between LR components

Performance Center Components

  • Administration Site: The Administration Site is used for administering the Performance Center system. From the Administration Site, you can perform tasks such as assigning user roles and privileges, creating and administering projects, and managing resource usage
  • User Site: The User Site is used for creating, managing, and running load tests. From the User Site, you can perform tasks such as designing and configuring load tests, configuring monitors, reserving resources, running and monitoring test runs, and analyzing test results
  • Utility Server: The Utility Server is the Performance Center License Manager and is also used for configuring monitor profiles and other maintenance services
  • Database and File Servers: The Database and File Servers form the infrastructure for persistent data within Performance Center. The Database Server stores information on users, projects, host information, and load tests. The file server stores the test scripts and test results
  • Performance Center Host: Performance Center hosts are used to control load tests, generate load, and analyze data. Performance Center hosts can be configured as Controllers, Load Generators, or Data Processors
  • Controller: The Controller is the manager of a load test. The Controller receives the scripts, their run-time settings, and a list of the load generators to use. The Controller issues instructions to the load generators including which scripts to run, how many Vusers to run per script, and scheduler settings. At the conclusion of the test run, the Controller collates the data. There is only one Controller per load test
  • Load Generator: Load generators generate load by running Vusers. The Controller dictates the manner in which they start and stop running. There can be any number of load generators for a given load test.
  • Data Processor: The Data Processor host is used for publishing information to the Performance Center Dashboard.
  • MI Listener: The MI Listener is one of the components needed to run Vusers and monitor applications over a firewall.
  • Monitors Over Firewall: Used to monitor servers that are located over a firewall.

The following standalone applications, which are included on the Performance Center installation disk, integrate with your Performance Center System:

  • HP Virtual User Generator: Virtual User Generator (VuGen) generates virtual users, or Vusers, by recording actions that typical end-users would perform on your application. VuGen records your actions into automated Vuser scripts which form the foundation of your load tests
  • HP Analysis: HP Analysis provides graphs and reports with in-depth performance analysis information. Using these graphs and reports, you can pinpoint and identify the bottlenecks in your application and determine what changes need to be made to your system in order to improve its performance.
  • SiteScope:  SiteScope is a data collector used for collecting performance data from network, application, database, and Web servers.
  • ERP and CRM Mediator: The ERP and CRM Mediator gathers and correlates offline transaction data for the ERP/CRM diagnostics modules.

See also:

Avoiding issues installing HP Performance Center

2 thoughts on “Performance Center : Architecture overview

Leave a Reply

Your email address will not be published. Required fields are marked *