We’re still testing but what we WANT to do is to use Windows Virtual Desktop and then publish the Epicor app so the app looks local but is running in Azure.
If doing it that way gives better performance I wonder why Epicor doesn’t do that for their Public Cloud users.
You really want to run this in your Active Directory and not Epicor’s. Since this is a part of M365, the licenses really flow to the end customer and not a provider.
Hi Everyone,
A notorious degradation of performance… could it be related to mismatched hardware sizing options between MS Azure Cloud and On-Premise (Physical/Virtual)? There is a myriad of hardware options available in MS Azure to chose from, and the recommended specs from official Epicor 10 Hardware Sizing Guide seem to be more focused on On-Prem (Physical/Virtual).
@Mark_Wonsil @rbucek @aaronssh @hmwillett
For those of you who have already made the move from On-Prem to (Azure) Cloud,
What type of Server Instance (VM Types) did you chose for your App and DB servers?
- General purpose
- Compute optimized
- Memory optimized
- Storage optimized
- GPU optimized
- High performance compute
Did you replicate exactly what you had on-prem 2 servers to 2 VMs or did you take a single server on Azure?
For the Storage/Managed Disks, did you take Standard HDD, SSD or Premium SSD?
How many disks did you add to your Epicor app/db server? Are you separating database files (mdf/ldf) into multiple disks as recommended?
Also for the disks (Storage Transactions), how did you determine how many Transaction units (10,000 transactions) you need?
Regards,
Hello @carlosqt,
As Epicor Dedicated Tenant SaaS users, we don’t choose the hardware - Epicor does. They have a min-Data Center within Azure. I sense it was a lift-and-shift from the previous host providers but now they aren’t even doing the hardware and rely on Microsoft’s consultants for this kind of advice.
IMHO, the performance is due to the architecture which assumes a nearby application server which hides the inefficiencies until you get to the cloud. When we get to Kinetic, I like to think the performance will be better. It does seem snappier on MES. The startup is a bit slow but again, it’s being launched by the rich client so hard to tell. Any improvement in performance for the Cloud users will lead to better performance on prem. You’re welcome. 
It’s purely latency-based for us.
Our Azure servers are far better spec’d and the architecture is better designed than what we had on premise since we got to start from scratch.