What size is your largest FSLogix profile?

What's the size of your largest FSLogix profile? Is the size causing any problems? Is the profile used on multi-session hosts? Where is the profile VHD - Azure Files (AD or EntraID), file server VM, Blob storage? 

I recently increased the limit to 50 GB for single-session hosts used by our developers, but none of them are using much over 30 GB yet. The rest of us are in a multi-session host pool, within the 30 GB limit. AD-joined Azure Files Standard, because we wanted to see how bad it would be. It seems fine for what we do. 

I'd like to know if there's a practical limit, besides cost. 

0

Comments (2 comments)

Avatar
Marcos Artiaga

Hi Peter,

This is very much a "your mileage may vary" situation, but regardless of the individual profile sizes of the users, we will always recommend using Azure Files Premium for FSLogix. Premium shares have a single digit latency SLA for read and write operations, while Standard shares do not. Premium shares also have higher IOPS and throughput capabilities. 

That's not to say that if you deploy on Standard shares, it won't work. It might be good enough. But if you start running into performance issues (long log on/ log off times) for example, it can likely be attributed to the performance of the share. Sometimes users may log in and get a blank screen as well. The number of concurrent users logged in may also contribute to this. So where 5 users are logging in and nobody is really complaining, that same deployment for 20 users may behave very differently.

Now when we talk about the actual size of the profile disks, even on Premium shares, once they start to get to 50GB or higher, there's usually a noticeable difference to the user on performance. That can also be compounded with the profile being on Standard file shares. 

Overall, I'd say to mitigate the possibility of future calls from upset end users, we will typically recommend Azure Files Premium for FSLogix and keeping the profiles under 50GB if possible. This may mean putting in certain policies to limit the size of the Outlook cache, prevent caching shared mailboxes, and setting OneDrive to download files "on demand" only.

Hope this helps!

0
Avatar
Peter Yasuda
(Edited )

Hi Marcos, 

Your comments are very helpful. To be clear, we are always using Azure Files Premium for client deployments. Our AF Std deployment was a test, although test environments have a way of becoming production. We are hitting a maximum of 15 users now, so the symptoms of performance issues are very good to know. We disable the Outlook cache; we didn't see a need for it when the AVD hosts are sitting so close to the Exchange servers. For myself, I use Outlook Web exclusively. 

Are the performance issues with large profiles on AF Premium the same as small profiles on Std? Slow login and blank screens? 

Thank you!

0

Please sign in to leave a comment.