web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Unanswered

Environment running low on memory, crashes when memory intensive task is started

(2) ShareShare
ReportReport
Posted on by 14
Hey all, 
 
Currently investigating an issue where a memory intensive task causes a AOS crash. 'OutOfMemory'.
 
What i am seeing is that the batch-aos is constantly running on low memory, and when the process is started it runs out of memory. 
 
We are aware of the issues with this memory intensive task, and have already taken steps to fix this issue. But for now the fix has not been released.
 
What i'am cuirious about is where is all the memory of the BatchAOS going before the task is started. Is there any way to retrieve this information? Cant seem to pinpoint a single activity in LCS. (bear in mind in quite new to the LCS monitoring)

See the task is started at 7:38:00 and causes a crash at 7:44:00. But before starting the available memory is already low. 


A few hours later(12:49), the memory has decreased some, but not nearly as low as 1300Mb:


Any way i can investigate further? 

Thanks!
Categories:
I have the same question (0)
  • Jonas "Jones" Melgaard Profile Picture
    4,986 Most Valuable Professional on at
    No, it's not possible to see exactly what is consuming memory or causing a memory leak in Microsoft hosted environments. My advice is to contact Microsoft Support and check whether this is a known issue or if something can be scaled.

    However, if you want to dig a bit deeper, you can take a look at this article: https://denistrunin.com/performance-powerbibatch/

    I built a dashboard similar to Denis’s at my former job to debug AOS Batch memory consumption. Maybe you can correlate the memory consumption with the batch schedule. Notice his "Batch tasks schedule" example.
     
  • Jouke Profijt Profile Picture
    14 on at
    So, status update.
     
    While not certain that the issue has been resolved, Microsoft support had given us information about running batch tasks which were taking up the most time/resources. 
     
    We've reorganized these batches to run at different times, as these seemed to have a conflict in the tables which were in use. 
     
    We also updated the batch-priority as all batches were running on low priority. Now most jobs run as normal priority, our problematic task which is quite important for the customer has been assigned reserved capacity. 
     
    After this change the task has successfully run 3 times for a larger set. 
     
    Only thing that we see now is that the BatchAOS's seem to restart every morning and the available memory still seems to decrease throughout the day:
     
    This might be normal behaviour? i'm not sure. 
     
     

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.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 451 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 428 Super User 2025 Season 2

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 239 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans