MSFT: [email protected]
ACU appears to have recently replaced core in compute performance descriptions for the various app service tiers. When did this happen and why? And where can we see an accurate performance comparison between ACU and core for app service? This exists for VMs, but that chart is ambiguous when applied to app services.
Edited: Removed PII with 'x'.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@AlexFiala, Thanks for the question! We are checking on this and will update you shortly.
@AjayKumar-MSFT 5 months later, any update yet?
Suchiman, We have already reached out to the product team and they would publish a blog detailing the change soon. Sorry for the long wait! Thank you for your patience and co-operation.
Could you please include if there is any difference between the Standard and Premium in CPU power? Looking at the ACU's; they're the same but I would expect the premium to be higher right? Or is that because of some vCPU:Core ratio found on this page: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/acu ?
In particular, they slap 210ACU at P1V2 (1 Core, 3.5GB) and 200ACU at S2 (2 Cores, 3.5GB), indicating that a single core of P1V2 is more than twice as powerful than a standard core, that's something i'd like to see benchmarks on.
Wow really still no explanation of what ACU means when it comes to App Service Plans?!? The link referred to by @Zenuka has to do with VMs. Not App Service Plans.
I see that Standard tier is A-Series compute equivalent, I use a S3 service plan and do some loadtest (some cpu work) with it, the performance is not good comparing to a B2ms VM. The document of VM indicates that A-series is suitable for dev/test, Standard app service is design for production but A-Series compute equivalent.