If possible, separate Virtualize and Data Repository. This is important for "future proofing" your deployment. This becomes especially important: - When Virtualize and Data Repository eventually compete for resources.
- If bad data repository happens to bring down the machine hosting Data Repository. If Virtualize and Data Repository are separated, this Data Repository failure won’t take the Virtualize server down with it
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, and the most common way users accomplish this is by installing them on the same machine, or two machines that are co-located as much as possible (e.g. 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 |