Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Virtualization Manager (VMAN) > VMAN 8.0 Administrator Guide > References > Reduce the memory requirements of Virtualization Manager

Reduce the memory requirements of Virtualization Manager

Table of contents
No headers
Created by Caroline Juszczak, last modified by MindTouch on Jun 23, 2016

Views: 8 Votes: 0 Revisions: 3

The minimum memory requirement is 8 GB, but more memory might be necessary to handle peak demands. You can reduce the memory requirement for collecting from multiple vCenters (VC) in these ways:

  • Schedule the configuration data collection jobs for the different VCs in a way that they do not overlap, by setting the start times at least three hours apart. This also means reducing the frequency of configuration collection to one or two times per day.
  • Instead of using the actual total number of ESX hosts in the environment, calculate an approximate number of hosts according to the formula:
    1. Take the largest number of hosts managed by a single VC instance.
    2. Add 15% for each additional VC in your environment, regardless of its size.

For example, if you have three VCs and the largest VC manages 90 hosts, your "proxy number of hosts" is 117.

117 = 90 + 0.15 x 90 + 0.15 x 90

The number of ESX hosts above is guidance only, and is based on a typical virtualization environment with approximately 10 VMs and one datastore per ESX host server. More dense environments require larger memory sizes.

Last modified
04:20, 23 Jun 2016