Hey everyone,
We were running Appvolumes 2.10 and logins were 30+ seconds depending on the number of stacks assigned to a user. In some cases (Visio as an Appstack), logon times would shoot to in excess of a minute. We then upgraded to 2.11 as part of a Horizon 7 rollout (with vSphere 6 U2) and the logon times increased! Ouch! All areas of the build (the core is very vanilla) were reviewed alongside the hosts, storage, network and DB, but with no obvious problem areas. Each time this was raised with VMware, it was acknowledged that certain parameters that were applicable in 2.10 were no longer acknowledged in 2.11 and as there were product limitations for 2.11, wait until 2.12 and there will be vast improvements!
Well, like others in the forum, during testing of Appvolumes 2.12, we are still seeing yet further slow down of logins!
We managed to improve the speed by dropping SSL, (setting to use port 80 from agent to manager), but the overall result is that logins are no better than where we stood before.
Interesting and unsurprisingly, stopping the svservice (AppVolumes) brings us back to circa 15 sec logins. However, just running the service even with no user stacks assigned adds about 10seconds to a typical logon so there seems to be an effective heavy penalty for it to merely check for user assignments, let alone attaching anything.
Im going to start investigating hardcoding requests to specific domain controllers in preference to using the domain fqdn in the configuration to see if that changes anything too. Will report back.
If anyone else has any similar experience or problems, please let me know as for us, 2.12 was considered to be the last roll of the dice for Appvolumes in preference to a rivals offering that seems capable of cutting our current logon times in half which for a userbase of 1000 multiplied by 15 seconds is the equivalent of 250minutes of lost productivity each time all users log on!
Thanks
Andrew