The deployment package installs vATD/vIS to your hypervisor host with a default memory size of 32 GB. This memory size setting determines the upper limit of memory space that vATD/vIS can use.
vATD/vIS has evolved to support recent Windows 10 builds. We've observed that the recent Windows 10 build tends to use more memory space. In the back-end of vATD/vIS, the Windows sandbox VM is created with a fixed memory space as 3 GB. vATD allows creating 8 licenses of Windows 10 Sandbox VM, which in total use 24 GB of memory out of the 32 GB limit.
The Email Connector is implemented as a VM running on the hypervisor. Email Connector VM runs in parallel with other Windows Sandbox VMs and is created with a fixed memory space of 4 GB.
In a busy environment, resource usage inside the Email Connector VM becomes high. This resource usage can lead to services and the entire system stopping reponding (crashing).
vATD/vIS has a resource usage warning feature, which raises a warning at 75% memory usage by default.
For example, you have 7 Windows 10 Sandbox VMs and an Email Connector on vATD/vIS. The total memory space used for the VMs is 7 × 3 + 4 = 25 GB. This 25 GB usage reaches the Windows 10 memory usage threshold.
In the back-end, there are several other mission-critical services. These services include database and web server, which run concurrently and also require memory space.
These processes also require a certain amount of memory space.
In these scenarios, the default 32 GB memory size isn't sufficient for smooth operation and you see the following issues:
- If you create 8 licenses of Windows 10 VM and install the Email Connector to vATD/vIS, there isn't enough memory space for the system services.
In this situation, a lack of virtual memory causes slow performance or processes to fail. Several vATD/vIS features then become unstable.
- vATD/vIS can't allocate more memory size to the Email Connector VM.
