Virtualization Manager Advanced Parameters
The following advanced parameters apply to Virtualization Manager data collection and can be added using:
Admin > Advanced > Parameters, described in Adding an Advanced Parameter. VMWARE_CONCURRENT_COLLECTION_COUNT
Valid Values: 0, 1, 2 (Default = 1)
If this parameter is set to 0, both the VMware inventory and performance collectors will collect entirely sequentially (e.g., collect a host, persist it, collect the next host, persist it, etc.). Setting this parameter to 0 will result in a slower collection, but the logs will be easier to understand.
If this parameter is set to 1, the VMware inventory collector will persist data for one host, cluster or VM while collecting data for another one.
If this parameter is set to 1 or higher, the VMware performance collector will persist data for one batch of hosts or VMs while collecting the next batch of performance data.
If this parameter is set to 2 or higher, the VMware inventory collector will collect from that number of hosts, clusters or VMs concurrently (but only one can be persisting at a time). This should improve the performance of the inventory collection, but at the expense of a possible increased load on the vCenter/ESX server.
This parameter works in conjunction with the
VMWARE_CONCURRENT_DATASTORE_COUNT parameter. Setting either to a value higher than 1 will give some benefit, but the greatest benefit is seen when both are set to 2. Setting to higher values gives diminishing returns in performance while probably further increasing the load on the vCenter/ESX server. For example, if both
VMWARE_CONCURRENT_COLLECTION_COUNT and VMWARE_CONCURRENT_DATASTORE_COUNT are set to 2, up to 4 datastores may be listed concurrently (2 per host).
VMWARE_CONCURRENT_DATASTORE_COUNT
Valid Values: 0, 1, 2 (Default = 1)
If this parameter is set to 1, the VMware collector will list datastores for a host sequentially.
If this parameter is set to 2, the VMware collector will list that many datastores for a host concurrently. This should improve the performance of the inventory collection, but at the expense of a possible increased load on the vCenter/ESX server.
This parameter works in conjunction with the
VMWARE_CONCURRENT_COLLECTION_COUNT parameter. Setting either to a value higher than 1 will offer some benefit, but the greatest benefit is seen when both are set to 2. Setting it to higher values gives diminishing returns in performance, while probably further increasing the load on the vCenter/ESX server. For example, if both VMWARE_CONCURRENT_COLLECTION_COUNT and
VMWARE_CONCURRENT_DATASTORE_COUNT are set to 2, up to 4 datastores may be being listed concurrently (2 per host).
VMWARE_DATASTORE_TIMEOUT_SECONDS
Valid Values: 0 or higher (Default = 0)
If this value is set to 0, the VMware inventory collector will wait indefinitely for datastore listings or an error to be returned from the VMware server.
If this value is set to a positive number, the VMware collector will cancel any datastore listing that takes more than the specified number of seconds. For example, if this parameter is set to 1800, any datastore listing that takes longer than 30 minutes will be cancelled.