Hello Steve,
I suggest to start with the TechTalk Performance Testing Approach (infopedia.eventbuilder.com/event;source=Dynamics_365_for_Operations_-_FastTrack_Tech_Talks) to understand our guidance regarding performance testing.
In case that a customer states in the Checklist that they saw poor performance in UAT, this is what we put into the assessment report:
Sorry to hear that you are seeing poor performance in the UAT environment. Here are some things to consider and actions to take before moving to production:
• Has performance been bad across all processes and users and times?
• Are there specific actions that are especially slow?
• Have you used the Performance timer to better understand where the time is spent?
• Have you taken traces to determine what contributes to poor performance?
• Have you used Environment monitoring to see if there are any locking or blocking issues, slow queries, or missing indexes?
• Do you have your most critical scenarios documented, including performance goals?
The most important point here is to understand that Performance is not Microsoft responsibility alone, it is a combined effort since performance can be affected by variables outside of Microsoft’s influence, including but not limited to your customizations, ISV code, system configurations, timing of batch jobs and integrations.
The project will need to decide based on their parameters how much performance testing is required and on which environment (Standard Tier-2 or Tier 4 or 5 performance testing environment).
Cheers,
Claudia Betz-Haubold
Microsoft FastTrack Solutions Architect
