vATD deployment package installs vATD to your hypervisor host with a default memory size of 32 GB. This memory size setting determines the upper limit of memory space vATD can use.
vATD has evolved to support recent Windows 10 builds. McAfee has observed that the recent Windows 10 build tends to use more memory space. In the back-end of vATD, 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 memory out of the 32-GB limit.
The Email Connector is implemented as a virtual machine running on the vATD's hypervisor. Email Connector VM runs in parallel with other Windows sandbox VMs and created with a fixed memory space of 4 GB.
In a busy environment, resource use inside the Email Connector virtual machine becomes high. This resource use can lead to services and then the entire system stopping reponding (crashing).
vATD has a resource use warning feature which raises a warning at 75% memory use by default.
For example: You 7 Windows 10 sandbox VMs and an Email Connector on vATD. The total memory space used for the virtual machines is 7 X 3 + 4 = 25 GB. This 25-GB use reaches the Windows 10 memory use threshold.
In the back-end of vATD, there are several other mission-critical services. These services include database and web server, which run concurrently and also require memory space.
Those processes also require a certain amount of memory space.
In these scenarios, the default 32-GB memory size of vATD is not enough 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, there is not enough memory space for vATD system services.
In this situation, vATD virtual memory, causing slow performance, or processes to fail. Several vATD features then become unstable.
- vATD can’t allocate more memory size to Email Connector VM.
