The memory consumption by vSphere-client service depends on many factors like the size of vCenter Server, the scale of the inventory, how many and what kind of plugins are used, and so on. Although the initial heap sizes of each services are determined during system boot as cloud-ram-size(.bat) -l shows, tuning may be required if the initial allocation does not fully meet the requirement of each environment.
To resolve this issue, change the maximum heap size manually:
You experience these additional symptoms: