CVAD session hosted desktops on a 2019/2022 server...
# citrix-cloud
s
CVAD session hosted desktops on a 2019/2022 server. Would you pick Azure B or D series machines?
b
D series
s
Why so if you dont mind me asking
b
CPU and memory requirements.
s
Say you needed 8 cpu and 32 gb of ram. Both B and D have the same cpu and mem. B has less IOPs and you dont need them. Would you go with D for any other reasons?
b
s
Thnx, Good to know. Last question. recommendation for trusted launch startup Azure vms or standard?
r
B series are "best effort" Never want to use those in production.
b
depends on your setup/needs. security is always good, (and a must for most of our customers). I use it.
s
we use d16ds_v5 - mainly because we use ephemeral disk and they fall into our RI's
d
B is burstable, you get a cpu quota, so all depending on load, if you have users that use more than 50% cpu on it, you will use all cpu quota, and the server will be so slow it will be unusable. I would only use B servers for anything like DC, storefront, cloud controller etc
šŸ™Œ 1
r
I've seen burstable (B) used for AD-servers with success but anything with variable load or customer wouldn't go near burstable. I've a badly maintained list of reference benchmarks on various instances D or F is the main choice people evaluate for VDI. N (with GPUs) see for GPU/graphics heavy CAD etc. And stuff like E-series see a bit in SAP deployments. https://www.eginnovations.com/blog/avd-deployment-azure/ towards the end has links to various comparisons - above the table most recent I've spotted. Citrix themselves use D and F in their reference architectures which means you have a very good baseline to evaluate success - and theoretically there is someone somewhere in Citrix familiar with troubleshooting that configuration.
We get an occasional support case when a customer uses a burstable in production - in a lot of tools CPU is just shown at % - so it looks like an application shooting up to 100% of CPU without the info the actual CPU available is less. If you do use burstable you should also monitor your CPU credit usage. Here's a blog on what a burstable running out of credit looks like CPU and credit wise https://www.eginnovations.com/blog/aws-ec2-monitoring-tools/ there can be options on burstable to carry on regardless and pay for credits that exceed your allowance - that can get hugely expensive rapidly so if go down that "brave" path always have credit monitoring in place is my warnings.
šŸ™ 1
m
I’m surprised nobody said N or E? In our projects the decision is always between E and N, because they have so much more RAM than the D series. And with the RAM hunger from modern apps, CPU is rarely the limit.
šŸ™Œ 1
r
@Marco Hofmann I mentioned E and N šŸ˜„
🫔 1