Performance Center deployments

This section contains examples of some of the deployments that can be used for configuring Performance Center on-premises or on the cloud.

Note: These examples are used to illustrate functional capabilities only. In a real deployment, you can mix and match components from the various options to create a deployment plan that best suits your needs.

For full installation and configuration instructions, see the Performance Center Installation Guide.

Basic deployment example

The basic deployment for Performance Center requires a Performance Center server, Performance Center host, load generators, and ALM back end components (including ALM server, database, and repositories).

Note: A load balancer is required only when you have two or more ALM or Performance Center servers.

Back to top

Over firewall deployment example

When testing applications that are located behind a firewall relative to the Performance Center server or host machine, you must configure an MI Listener, a load generator over a firewall, and possibly a monitor over a firewall.

Back to top

Advanced deployment example

This deployment illustrates the ability to integrate Performance Center with various Application Performance Management (APM) tools, as well as integrating with Kubernetes or Docker Swarm for dynamic provisioning of load generators (see Dockerized (load generators) deployment example below).

Back to top

Cloud (load generators) deployment example

Performance Center enables provisioning of load generators in the cloud using your AWS or Azure cloud account. For more details, see Manage cloud hosts.

Note:  

  • The ports used in this diagram are the common HTTP ports. You can configure the cloud load generator ports as required.

  • For the most secure load generator connectivity, use SSL with a client certificate.

Back to top

Full cloud deployment example

You can deploy Performance Center in the cloud provided you follow the system requirements and use the relevant ports. Load generator provisioning is supported with AWS and Azure. For more details, see Manage cloud hosts.

Note:  

  • To improve performance, it is preferable to deploy the ALM server, Performance Center server and hosts, and the database in the same region.

  • The required ports should be open for incoming requests to the relevant server.

  • Cloud load generator ports are configurable. When all the components are in the cloud, the ports to use are defined by the cloud provider (they are not based on internal IT policies).

  • For the most secure load generator connectivity, use SSL with a client certificate.

Back to top

Dockerized (load generators) deployment example

Performance Center enables provisioning Dockerized (elastic) load generator images using a Docker Swarm or Kubernetes orchestrator (the orchestrator provisioning the load generators and the AUTs can also be cloud-based). For more details, see Manage elastic load generators.

*For the required ports, see the Docker Swarm or Kubernetes documentation.

Back to top