This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
Hello,
I deployed tabular model to AAS. This model is getting data from Azure SQL Database using M code.
Lets say, the size of the model is 1GB.
Processing of the model takes another 2GB (but its only one short-time peak).
But here is the interesting part:
After processing is done, the overall memory in AAS is showing 2GB, not 1GB.
This 1GB increase is due to "M Engine memory", which doesnt drop to 0 after processing, but keeps at 1GB and stays at this level.
When I reset the AAS (pause and start), this "M Engine memory" is cleaned.
But only till the next processing.
What to you think, is this behaviour normal?
Why the "M Engine memory" doesnt go back to 0 after processing?
Thanks in advance.
Hi @BohusUhrin ,
It should be related to AAS memory properties.
Analysis Services pre-allocates a modest amount of memory at startup so requests can be handled immediately. Additional memory is allocated as query and processing workloads increase.
Check the reference below:
Best Regards,
Kelly
Did I answer your question? Mark my post as a solution!
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |