Forum Discussion
Power BI report Server slow
I am making some configurations in the Power BI Report Server to improve the performance of the Report that is in "Import mode".
When users open the reports, the Analysis Server service ends up consuming 100% of memory.
I would like to know if I put the Power BI Report Server service account in the "Increase a Process Working Set" and "Lock Pages in Memory" settings, would it help the performance of the Reports?
Hi denisciola ,
If your server is dedicated to Power BI Report Server, you can enhance performance by increasing the TotalMemoryLimit in the msmdsrv.ini file to 90–95%. This change enables the Analysis Services engine to use more of the available memory, thereby improving report efficiency.
Recommended
- TotalMemoryLimit - 90–95%
- LowMemoryLimit - Typically 60–70%, adjustable based on workload
After implementing these changes, it's essential to monitor system memory usage to ensure stable performance. Even on a dedicated server, tracking key performance counters will help verify that the OS retains sufficient resources.
Regards,
Yugandhar.
you're saying that the SSAS service consumes 100% of the memory.
IMHO this could mean:
- report are too expensive
- memory is not enough for your workloads
- or both
how much memory has this server?
most of the time bad performances come from bad report/model design.
for example:
- useless data imported (this amount of data will reside in RAM)- wrong data types
- bad DAX patterns
- ...
have you alredy check the reports with devs?
8 Replies
denisciola You can try performance tuning your report server by referring the below article. Let me know if that helped !
https://www.gigxp.com/powerbi-report-server-performance-tuning/
Hi denisciola ,
Thank you for engaging with the Microsoft Fabric Community. In additon to Jai-Rathinavel response, here are some ways to optimize it and prevent performance issues.
1. Grant additional privileges to the Power BI Report Server service account, such as Increase a Process Working Set and Lock Pages in Memory, to improve memory access. Monitor the server to ensure other processes remain unaffected.
2. For reports in Import mode, reduce memory usage by removing unused data, applying filters, or using aggregations. Schedule refresh times during off peak hours to alleviate memory strain.
3. Adjust the msmdsrv.ini file to limit the Analysis Services engine memory usage to around 75% of total RAM.
4. If memory issues persist, consider adding more RAM or switching to DirectQuery mode, allowing Power BI to pull data directly from the database.If my response solved your query, please mark it as the Accepted solution to help others find it easily.
And if my answer was helpful, I'd really appreciate a 'Kudos'.
Thank you for your feedback
Regarding the item:
If my server is exclusively for Analysis Services, can I configure the Power BI Report msmdsrv.ini file to use 95% of the memory, or is it better to leave it at 75%?
The parameter I should change is TotalMemoryLimit?
C:\Program Files\Microsoft Power BI Report Server\PBIRS\ASEngine\msmdsrv.ini
Hi denisciola ,
If your server is dedicated to Power BI Report Server, you can enhance performance by increasing the TotalMemoryLimit in the msmdsrv.ini file to 90–95%. This change enables the Analysis Services engine to use more of the available memory, thereby improving report efficiency.
Recommended
- TotalMemoryLimit - 90–95%
- LowMemoryLimit - Typically 60–70%, adjustable based on workload
After implementing these changes, it's essential to monitor system memory usage to ensure stable performance. Even on a dedicated server, tracking key performance counters will help verify that the OS retains sufficient resources.
Regards,
Yugandhar.
you're saying that the SSAS service consumes 100% of the memory.
IMHO this could mean:
- report are too expensive
- memory is not enough for your workloads
- or both
how much memory has this server?
most of the time bad performances come from bad report/model design.
for example:
- useless data imported (this amount of data will reside in RAM)- wrong data types
- bad DAX patterns
- ...
have you alredy check the reports with devs?
Hi denisciola ,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi denisciola ,
Has your issue been resolved, or do you require any further information? Your feedback is valuable to us. If the solution was effective, please mark it as 'Accepted Solution' to assist other community members experiencing the same issue.
Hi denisciola ,
I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.
Thank you.
