We noticed that hardly any user is log into the D365 FO application, but the memory consumption is still high almost 80% . Seems like the memory once consumed is not later released by the system and most part of it is consuming by AX Service process only. Is there any hotfix or solution available?
Another thing is that there is uneven users load balancing by the system, two of the AOS servers take 20-30 users, while one AOS takes 200 users. Is there is any configuration changes available in config Template or in application to adjust these?? Moreover, Windows error reporting service also takes too much CPU consumption.
The environment is on-premises. SQL version is 2016, FO version is 10.0.31.
What is the memory consumption when all servers are restarted? If the memory consumption is constantly increasing and not released, this can have multiple causes and reasons. Some memory can be reserved. It can be due to customizations or another bug. As you are running your operations on an old version, you can check what happens when using a current release. At this moment, the current version is 10.0.38. Your version 10.0.31 is already out of support.
If there is no difference, then you can start monitoring the memory consumption in time.
In the past, on version AX2012, there was a memory leak where the posting of a journal consumed some memory, but only half of it got released after posting. You can try to find the process in F&O that is taking memory and not releasing it after a job is completed.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
44
Share
Report
All responses (
Answers (
