You can tune the vCenter Hyperic vApp for large deployments. A large deployment is defined as one in which the vCenter Hyperic server manages more than 250 platforms.

On the vCenter Hyperic server platform, add the following parameters to /etc/security/limits.conf.

hyperic user    soft     nofile     8192
hyperic user    hard     nofile    16384

On the vCenter Hyperic database platform, add the following parameters to /etc/security/limits.conf. The custom user variable is usually hqadmin.

custom user    soft     nofile     8192
custom user    hard     nofile    16384

Restart the vApps after saving the changes to /etc/security/limits.conf.

On the vCenter Hyperic server platform and on the vCenter Hyperic database platform, add the following parameters to /etc/sysctl.conf.

net.ipv4.neigh.default.gc_thresh1 = 1024
net.ipv4.neigh.default.gc_thresh2 = 4096
net.ipv4.neigh.default.gc_thresh3 = 8192

net.core.rmem_max=33554432
net.core.wmem_max=33554432
net.ipv4.tcp_rmem=4096 87380 16777216
net.ipv4.tcp_wmem=4096 65536 16777216
net.core.netdev_max_backlog=50000

After saving the changes to /etc/sysctl.conf, reload the file with the command root@localhost# sysctl -p.

Increase the virtual machine memory to 12GB.

Add the following to hq-server.conf.

server.java.opts=-Djava.awt.headless=true -XX:MaxPermSize=192m -Xmx8g -Xms8g -XX:+HeapDumpOnOutOfMemoryError -XX:SurvivorRatio=12 -XX:+UseConcMarkSweepGC -XX:+UseCompressedOops -Xmn4g
tomcat.maxthreads=3000
server.database-maxpoolsize=400

Increase the virtual machine memory to 16GB.

Edit /opt/vmware/vpostgres/9.1/data/postgresql.conf as follows.

shared_buffers = 8GB
effective_cache_size = 2GB
max_connections = 410