Best Practices/tuning guide for FMS & FgLAM (4323778)

Is there a optimization document or best practice guide that will help us configure the FMS server and FgLAM for the best possible performance?

We have 2 virtual center with 150 esx host on each of them as well as about 3,500 VM's on each VC. 

WORKAROUND:

Please find the best practice guide for VMware agent & Agent Manager configuration:

FMS performance tuning:

Agent Manager:

Monitoring more than 4000 virtual machines from a single agent host

The Agent Manager JVM usually requires additional memory to monitor more than 4000 virtual machines. The total number of virtual machines is the total from all vCenters that will be monitored from all VMware Performance agents running on the Agent Manager.

JVM memory requirements for VMware Performance agents are calculated using the following formula:
512 MB + 0.5 MB/VM

According to the above formula, monitoring 4000 virtual machines requires 2560 MB of memory:
512 MB + 2048 MB = 2560 MB
This is the default setting for agents deployed on 64-bit systems.

In FUTURE,  if the number of VM's increases to 8000, requires 4608 MB of memory:
512 MB + 4096 MB = 4608 MB
This requires the default agent setting to be changed.

How to change default settings?

To change the JVM memory settings:

On the agent machine, open the agent.manifest file for editing. The file is located in the /agents/VMwarePerformance/5.6.15.1-5.6.15.1-/config directory.
Locate the following line:

jvm-memory min="2560" max="2560" units="megabyte"/>

Set the min and max attributes to 4608 MB:

Delete the existing deployed negotiation configuration settings directory:

/state/default/config/deployments

Restart the Agent Manager/FgLAM for these settings to take effect.