In general VMware always recommends to assign at least 10GB of memory to each View Connnection Server when deploying View in production with more than 50 and up to 2000 desktops per Connection Server . There is also a a minimum requirement of 4GB of memory if you only want to deploy 50 desktops or less per Connection server.
Until version 5.3 of Horizon View the installer of the Connection Server automatically set the JVM heap size to a static amount of memory dependent on the amount of memory installed in you server. For example if your server has less then 10GB of memory installed the JVM heap size was set to 512MB. You even get a message at the end of the installation of Connection server that the system is configured with reduced resources due to the limited amount of memory.
So if you configured your Connection server with 4GB of memory at the beginning and later changed it to 10GB, because you added more desktops, the JVM heap size needed to be changed. While there are some guides how to do this manually it is recommended to reinstall the View Connection server software to get the JVM heap size right.
Now with version 5.3 of Horizon View the JVM heap size is automatically adjusted to the optimal size on each start of the View Connection server. No need for manual adjustment or reinstalling the Connection server.
As additional help every now and then you get an event log warning when your View connection server is not configured with the recommended amount of memory.
Update: To check if the JVM heap size was changed after adjusting the amount of physical memory available just have a look inside the current Connection server debug log file located under %ProgramData%VMwareVDMlogs, e.g. debug-2014-01-08-145917.txt.
If you configure your server with less then 10GB of memory the following entry should be found:
2014-01-09T09:32:06.072+01:00 INFO (09A8-0C18) <Service Main Thread> [ws_TomcatService] The service 'TomcatService' is started 2014-01-09T09:32:06.072+01:00 DEBUG (09A8-0C1C) <javabridge> [ws_java_bridgeDLL] Java heap size configured to -Xmx1024m -Dcom.vmware.vdi.SmallPhysMemory=1
If you configure your server with 10GB of memory or more the following entry should be found:
2014-01-09T09:42:47.696+01:00 INFO (0A94-0C14) <Service Main Thread> [ws_TomcatService] The service 'TomcatService' is started 2014-01-09T09:42:47.696+01:00 DEBUG (0A94-0C18) <javabridge> [ws_java_bridgeDLL] Java heap size configured to -Xmx4096m