Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We installed a new AOS. During our testing we found the new AOS to be slower than the prior in all tests, technical and end-user – even though both virtual machines on the same ESX host. We noticed that they have two different values for “Ticks per second” when we use the code profiler and our test results are slower in the VM which has the higher ticks per second. We need to know why the new VM performs worse than the one. My understanding is that ticks per second represents the clock speed. The code which creates that value is in the core, not visible in X++.
• Everything at the hypervisor level says that the CPUs are the same
• The VMs are sitting on the same ESX host
• Inside the virtual machines they are both reporting the same CPU
• AX server and client configuration files have the same settings (except for server names)
• AX code and data are the same (the new AOS is hosting a copy of code and data)
When using Dynamics AX virtual machines e.g. with ESX you need to check if you are not over allocating resources. If you have physical 8 cores and assign to two AOS machines each 6 cores, the machines gets slower when they have to share the cores.
The tick count can be caused by many factors. You have to do some monitoring on CPU, memory and disk read/write usage. Also check SQL query times.
Thank you for the reply. This VM in question only has the AOS service role. We have tested the SQL query times and the disk read and write speeds. So that leaves the AOS VM itself as the problem. The VMs are hosted for us in the cloud and our provider assured us that the VMs are all on the same ESX host, so from that standpoint I'd expect all of the VMs to be performing equally, but we don't see that. And the ticks per second on the new VM is exactly 4 times that of our existing AOS virtual machines. Hopefully that clarifies the problem.
Are there any concrete tasks that I can take to try to resolve it?
Hi Dag III,
When the hardware is configured equally, it could be over allocating of resources. Probably you can monitor on CPU wait times. Do you also have the option to monitor the ESX host?
Business Applications communities