Performance tuning options for Microsoft Dynamics 365 Finance and Operations
Areas which could be tune to support high performance need:
- Data management
- use data entities for bulk import/export and
- Use parallelism (multiple threads)
- Execute in batch
- Cleanup staging
- Batch
- Tune batch
- Specify max threads per batch server
- Use batch groups and allocate batch servers
- Avoid batches running too frequent
- Schedule batch during less load (night time)
- Use active periods for batch (PU21+)
- OData
- Do not use for large volumes
- Best case for real time calls
- Try not to use with PowerBI (use entity store or BYOD)
- Index (impacts IO)
- Use queries with indexes
- Follow regular index maintenance
- System job from Pu22+ and initiate index maintenance from within D365FO
- Could also do one by one from LCS environment monitoring
- Number sequence
- Use pre-allocation where possible
- Set based operations
- Tune your code to use set based operations rather than row by row
- Data cache
- Use CacheLookup wisely
- Atleast one unique index
- Ensure primary index is always unique
- Cleanup
- Batch history
- DMF staging
- Notification
- Journal
- Advance warehouse
- Work
- Wave
- Device and session activities
*This post is locked for comments