...
The following diagram shows the recommended architecture for a deployment with three Virtualize servers and CTP. Note that the "Server n" icons in the lower right corner represent any number of additional servers (as appropriate for your environment).
We recommend the following hardware for the Virtualize, Data Repository, and CTP server machines:
Virtualize
- CPU: 8 core
- RAM: 32 GB or higher
- Dedicated disk space: 300 GB or higher
Data Repository
- CPU: 4 core
- RAM: 32 GB or higher
- Dedicated disk space: 300 GB or higher
...
| icon | false |
|---|---|
| title | Virtualize and Data Repository Deployments |
while three Virtualize servers are shown here, you can have as many as you need.
Desktop users should develop assets using their local Virtualize desktop, then connect to a Virtualize Staging Server to test the assets in the staging environment. They will be able to monitor events on the Staging Server and debug their assets then, when a virtual asset is ready, check in the changes to the source control management (SCM) system.
Assets on Production or Performance servers should be updated through the SCM. This ensures that the behavior and performance of assets running on those servers is not affected by development of virtual assets and helps keep the product/performance servers stable. Performance servers should be configured based on the principles outlined in Performance Tuning a Virtualize Server. Updates of assets from the SCM could be scheduled or on demand, based on what best fits the current needs. For example, deployments in Kubernetes might use an initContainer to pull from the SCM while those using a physical server might have a job that runs on demand from an automation server.
Using a single server for both staging and production has inherent risks. While it can be done, it is not recommended for several reasons. For example, a desktop user could redeploy an asset while a test is using the server, causing failures, or monitor an asset during a load test, causing a decrease in throughput. Without a separation of staging and production environments, it's possible that a desktop user's development of assets could negatively impact automated tests or load testing.
It is recommended to minimize the network latency between a Virtualize server and a Data Repository server as much as possible. Network latency between the processes can negatively impact the performance of the Virtualize server under load
...
. The most common way
...
this is done is
...
to install them on the same machine, or two machines that are co-located as much as possible (for example, same data center region). The Data Repository server can consume a large amount of memory, so when installing it on the same machine as a Virtualize server, it is advised that the machine have at least 32GB RAM.
We recommend the following hardware for the Virtualize, Data Repository, and CTP server machines:
Virtualize
- CPU: 8 core
- RAM: 32 GB or higher
- Dedicated disk space: 300 GB or higher
Data Repository
- CPU: 4 core
- RAM: 32 GB or higher
- Dedicated disk space: 300 GB or higher
CTP
- CPU: 4 core
- RAM: 8 GB
- Dedicated disk space: 150 GB
...