
Hi,
I will soon start in a new AX project as platform owner. The project handles AX2012 R3 financials, and has already been started by AX partner in Finland.
For this platform, we will propably later add new AX instances.
When I start in the project, the actual AX installations (db, file servers, AOSes, SSRS and clients) can be seen as a black box. I will have no idea how they are configured, and I'm pretty sure the existing project documentation hardly includes any comments about the choices made for the platform.
As I'm quite suspicious, and also familiar with many types of performance issues with AX, I would like to hear your opinions, what could be the bottle necks for the AX?
I will, of course, analyse the results of AX project data gathering tool (nmb transactions, users, modules etc), and see how well the current platform matches the suggested configuration. I also have read different check lists for the performance issues (like http://blogs.msdn.com/b/axsupport/archive/2014/09/05/ax-performance-troubleshooting-checklist-part-1a-introduction-and-sql-configuration.aspx) Basically, I would like to ask your experiences, what parts of the AX installation proved to be hardest to measure, or fulfill the performance demands?
Have you noticed any special issues with R3? Will it be worth the effort to engage the newly released R3 CU8, when the project has been started with R3 CU0?
With my current project we have noticed the biggest issue is the communication speed with disks, and when that is poor, everything seems to be slow..
Do you have any suggestions for useful blog entries discussing the performance issues with AX2012 R2 or R3? I might have missed them :) Or, is there somewhere, a collection of useful links?
I hope I will have a chance to collect my experiences with this project to my blog... If I do, I will inform you where to read the story of the spiky hedgehog fighting windmills, and learning many new things.
*This post is locked for comments
I have the same question (0)Hi Emmi,
There is no simple way to answer your question, but I will say risk of impacting performance are:
1. Integration
2. Batch Processes
3. Reports
So you need to test as much as possible and allocate specific AOS for each workload.
For Checklist, see the recent post here:
For Pre Go Live To do list, you can read my blog serie here:
blogs.msdn.microsoft.com/.../top-10-tips-to-prepare-your-dynamics-ax-2012-go-live-series-13
Regards,
Bertrand