Vsphere webclient 5.5 very very slow, any solutions?

[sunny1986]

Dear all,

I have deployed ovf template 5.5 for vcenter, I have deployed 6 virtual machines in an ESXi host which has 24 GB RAM, 3 GHZ x 4 CPUs, 274 GB HDD, whenever users access the vcenter via webclient, they always complain of slowness, where is the experience is better while working on Vsphere client. I followed some of resolutions provided by this link Re: Very slow performance with the vSphere Web Client, but still unable to experience better performance. Kindly let me know what is the problem and what is solution to it, also please advise if there is any resource constraint for 6 virtual machines here.

[JPM300]

The biggest contributing factor other then resources on your vCenter is the database.  If it is the appliance and using the internal database there isn't much you can do.  Same thing goes if your running SQL Express on a Windows box.  However if your Database server is a full blow SQL copy you can try boosting its vCPU count and or memory.  Currently Vmware is also working on improvin the web client experience for the next revision as well.  Till then in most cases most people are using a split approach where they dabble for some things in the web client, while still loading the VI client for others.

[vThinkBeyondVM]

Hi Friend,

Please refer some blogs to improve web client performance.

http://www.vspecialist.co.uk/improving-vsphere-web-client-performance/

Improve vSphere Web Client Performance | Tom Fojta's Blog

http://ryanmangansitblog.com/2014/01/31/improving-vmware-vsphere-web-client-performance/

[sunny1986]

Dear Vicky,

Most of these posts say that we have to increase JVM heap size, but I am using appliance to deploy vcneter, how to increase JVM size in appliance?

[JPM300]

How to change JVM Heap size

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=206609...

Hope this helps

[vThinkBeyondVM]

Exactly I was going to point out above KB for JVM heap size config. ////

Please explore above KB given by JPM300.