I have deployed VCSA 6.5 last month at my client place but now they are facing very much issues while accessing the web client. I have also found that it takes too much time to fully load the vSphere web client.
All the operations are performed at very slow. Many times i have seen that if i perform anything it will get completed but it doesn't appear in recent tasks.
In short we are facing very slow performance with vSphere Web client in vCSA 6.5.
If anyone is having the same please share the information or steps by which we can improve the performance.
Maybe of help.
The vSphere Client is written in an HTML5-based language and frameworks supported by all browsers. However, different browsers have different performance characteristics regarding the HTML5 standard. In particular, performance with Internet Explorer 11 can be slower than with other browsers, because of the rendering engine that Internet Explorer 11 uses. If you experience such issues, try using another supported browser.
I performed a migration from vCenter Appliance 5.5 to vCSA 6.5... the problems began pretty much immediately. SLOOWWWWW slow slow... timeout errors all over the place.
We struggled for weeks with frustration.. tried IE, Chrome, Firefox, tried HTML5 and Flash... some days it was not even usable and others it was just good enough to get by. It's pretty much the same story as I've read on so many Google results.
We were ready to give up and go back to the 5.5 appliance... who cares if it's EOL this year, the 6.5 was practically unusable. A disaster recovery would have been impossible. 5.5 would have at least gotten us by long enough to switch to Hyper-V.
We don't have a huge domain, 400 users and our VMware environment is 12 hosts. But check this out;
The problems stopped immediately after we removed our LDAP identity source. Seriously, that's all I did.
There are only three of us that manage vSphere so we switched to local authentication and have our usernames in the vsphere.local domain. Currently I have no plans to re-enable LDAP as an identity source.
I hope this helps another sysadmin.... this was one of the most frustrating problems of my relatively short tenure, but the solution is simple enough it could help you too. Good luck!
Curtis found his solution but unfortunately, this will not work for us. Our environment has hundreds of hosts and thousands of guests along with a great deal of support folks with various levels of access inside the environment. What we sincerely need is a root cause and fix for this. We're running 188.8.131.5200 and both the flash and HTML clients are horribly slow. Deploying a server today (large SQL server with 14 drives) it took me almost 2 hours to trudge through all the editing of all the settings and drives to the point I could power on the server. This is a huge hinderance to our job performance. This is not sustainable. In most smaller deployments that aren't specialized like this one-off, I've resorted to PowerCLI to deploy systems to avoid using the (virtually unsuable) client.
How I miss the fat-client days.... Please, please, PLEASE tell us you are resolving this issue.
DNS resolves for ours. We have a server name registered in DNS and them an alias pointing to it for "vCenter" The problem exists whether we use the actual server name or alias.
Which one? We have hundreds. If you mean the host with vcenter on it, yes, that resolves forward and backward. All hosts are set to an internal time server which updates from ntp.org. Host with vcenter shows enabled and running. Time matches vcenter within 1 sec. This also matches the LDAP controllers time and configuration.
Each task (such as edit settings) for a VM guest is taking seconds to display any options related to the click. Browser and versions of any browser aren't improving or diminishing performance. vcenter isn't showing any issues with co-stop, ballooning, etc..... CPU (ready/usage avg 12%, no spikes over 21%), memory (8.32 GB of 32 GB active), disk (avg 4 sec latency) or network (avg. 12k of 10G).
Rebooting vCenter provides little improvement for a short interval. All scheduled maintenance not running during normal business hours. No issues or triggered alarms.
*EDIT* Also of note, the web client is running on a server in the same data center via RDP session. Both the management server and vcenter are on the same VLAN, same dvSwitch and same cluster.
We cannout pinpoint why response time is this slow.
Take a copy of this file .
Can you update the below file ? TAke a snapshot and modify it.
Modify this line in the file .
#firstboot_name cloudvm_name ciswin_name customMB tinyMB largeMB CompressClassSize StacksizeKB tinyGCThreads largeGCThreads
ngc_firstboot vsphere-client vspherewebclientsvc 0 597 1536 256 320 1 4
To CustomMB to 3072 and CompressClassSize to 512 .
Then restart web-client service.
service-control --stop vsphere-client
service-control --start vsphere-client
Please update if this helps. If not collect the logs once you observe the issue.