Recommended Azure and AWS performance specifications are as follows.
Azure
The performance requirements for Harmony Enterprise running in Azure are highly dependent on how many concurrent Windows Virtual Desktop (WVD) users you expect to have, and how demanding their workloads are. In the table below we provide rough guidelines for selecting your virtual machine (VM) database specifications, but we encourage you to experiment with the following parameters to find a combination that provides the best balance of performance and cost savings for your organization.
- Number of session hosts — you can add more VMs to spread your users across more hardware
- ‘size’ of session host VMs — you can select a size with more RAM and vCPUs if your performance is sluggish
- Database vCores — you can modify the min / max vCores for your Azure SQL DB to increase database throughput, if for example, users find that it takes too long to save and load well data.
| Component | Configuration | Comments |
|---|---|---|
| WVD session hosts | Standard D8s v3 | 8 vCPUs, 32 GB memory |
| Database Server – Windows 2016 Data center (SQL Server 2014 & higher) | General Purpose: Gen5, 8 vCores | |
| Azure File Share | 2 GB of allocated space per WVD user | You may need to increase your file share, if your user’s FSLogix profiles grow over time |
| License Server | Standard_B1ms | Standalone VM, always on |
AWS
AppStream 2.0 must first have a base image created with Harmony Enterprise installed and configured. The base image is then used to create a “fleet”. A fleet spins up instances for each user that connects, which means the number of users should not affect the fleet performance, provided the fleet has been configured with desirable performance levels.
As such, an important parameter that needs to be considered is capacity. This is the number of instances that are on, which equals the number of users that can connect to the fleet at a given time. AppStream 2.0 has auto-scaling, which can increase or decrease capacity as necessary. For more information, see AWS documentation.
| Component | Configuration | Comments |
|---|---|---|
| AppStream 2.0 Fleet | stream.memory.xlarge | Make sure to specify minimum and maximum capacity, as necessary |
| RDS Database with SQL Server (with your choice of SQL Server Edition) | db.t3.large | Allocate enough space for your database needs. Note that SQL Server Express Edition only supports a maximum of 10 GB. SQL Server 2016 or later is necessary for well-based security. |
| License Server | t2.micro EC2 Instance | Simple license server, always on |