Hi,
I wanted to post my findings here after recently deploying a PoC and reading this community post - App Volumes 4.0 performance
Deployed environment:
Horizon 7.11
AppVol 4 (latest)
DEM 9.10
FSLogix 2.8 (latest) - Profile and Office 365 container.
Windows 10 1909
First off to use App Volumes and FSlogix you have to add the exclusions into the snapvol.cfg file mentioned in this post -https://www.vcloudinfo.com/2019/08/vmware-app-volumes-and-fslogix-container-conflicts-resolved.html
Using App Volumes 4.0 with or without FSLogix resulted in poor VM performance and poor login times. I used full DEM personalization and dropped the FSLogix containers entirely to test there wasnt any conflicts and VM responsiveness was still poor. I was seeing behavior such as the svservice taking an age to process and then windows explorer constantly refreshing and flashing when it finally logged in. Also just browsing around the C:\ or launching apps (even base image apps) was really slow.
Login times were 1m30+ with App Volumes 4 so for good measure i upped my vCPUs to 4 per instant clone and this made no difference. FSLogix on its own with no App Volumes and a few apps installed within the base image was much faster about 40/50 seconds login and rapid responsiveness. I decided to create a new base image from scratch, again as always using the techzone optimization guide to rule out any base image issues and i also deployed App Volumes 2.18. Im now happy with the login times / VM performance & responsiveness using FSLogix containers and App Volumes 2.18. I had high hopes for 4.0 with the new features and "improved" performance but was bitterly disappointing with the outcome from my testing. Has anybody else played around with 4.0 yet?