1. I would expect the profile to load much quicker on second login compared to no writable.
What I'm seeing is that there is almost no improvement.
Using VMware Logon monitor I would have suspected the shell load time to drop significantly on second login
as the profile doesn't have to be created. However I'm seeing a gain of 2 or 3 seconds in shell load time on average.
This doesn't offset the attaching of the writable volume which takes 7 seconds on average.
Although it is a little bit quicker (depending on what W10 version you are using, we are using CB version) it is not that much. When logging in the writable needs to be attached and processed during logon after which Appvolumes releases that same logon. The writable won't help you with logintimes, it will help you with user settings.
2. During communication setup with the manager between sending the logon and sending the command to attach the writable I'm seeing a 3 second gap
where the agent is doing nothing. This is in between the logon and sending of the attach command.
During logon the agent sends a message to the Appvolumes Manager. The Manager checks to see what Appstacks it needs to attach and checks if you have a writable. Looking at the amount of appstacks, the groups used for assigning and the number of users in that group it can take up to a few seconds before Appvolumes Manager sends a request to the VCenter server (or ESX host depending on your configuration) for attaching the VMDK's. This all can take from 2 to up to 20 seconds depending on your settings and lots of more variables.