Virtualization

This topic is only applicable to Archer on-premises installations.

Virtualization creates a virtual, rather than actual, version of an operating system, a server, a storage device, or a network resource.

Completing the following tasks at regular intervals is recommended:

• Follow accepted IT industry best practices for configuring, monitoring, and maintaining virtual servers.
• Keep the allocation of your virtual machine (VM) host below 100% of its physical capacity.
• Leave at least 20% of the underlying host machine’s physical capacity available to absorb usage spikes.
• Use at least 24 GB RAM on dedicated VM host hardware for a large environment configuration. If your virtual environment configuration does not support 24 GB RAM, consider adding more VMs to compensate the physical system configuration requirements.
• Set resource reservations for processor and memory to ensure availability for the VMs running Archer. Adjust these reservations later to tune performance.

Completing the following tasks is recommended if your environment is failing:

• Employ multiple processor cores for the Web Server. Microsoft Hyper-V and VMware vSphere products can support 4 or more virtual processors in guest mode, but default to 1.Adding at least 1 virtual processor to the default (for a total of 2 or more) is recommended due to multithreading in Archer and thread pooling by running under ASP.NET. For more information on threading, see Job Engine Service.
• Dedicate spindles or a storage area network (SAN) to lessen the likelihood of disk or input/output contention issues.