Forum Discussion
On-Promise Gateway very Slow
If your report is using Direct Query, it could be slower than if it were using Import mode because the queries are being executed directly against the data source in real time. However, there are several things you can do to improve the performance of your Direct Query report:
Optimize your query: Make sure your query is as efficient as possible by limiting the amount of data returned, avoiding unnecessary joins or subqueries, and using appropriate indexing.
Use query folding: Query folding is a feature in Power BI that automatically converts your query to a more optimized form before sending it to the data source. To take advantage of query folding, make sure your query meets the criteria for folding, such as using simple filters and not using custom functions.
Increase the capacity of your server: If your report is still slow even after optimizing your query and using query folding, you may need to increase the capacity of your server. This could involve adding more RAM or upgrading the CPU.
Consider using Import mode: If your Direct Query report is still too slow, you may want to consider using Import mode instead. Import mode allows you to import data into Power BI and store it in memory, which can significantly improve performance.
Monitor the performance of your report: Use the Performance Analyzer feature in Power BI to identify bottlenecks and slow-running queries in your report. This can help you pinpoint areas that need improvement and optimize your report for better performance.
By following these tips, you should be able to improve the performance of your Direct Query report and make it run faster.
Hello,
thank you very much for your inputs.
My query is in Import mode now, I am using a dedicated server AWS T3.Large 16 Gbs RAM( As requested by MSoft).
Slownees appear to be between Power BI Service and End user.
Best regards,
Diogo Dalla
- edhans3 years ago
Community Champion
If it is still slow for end users after converting to import, how large is the model? Is it in a Pro workspace? And again, could be a service->your network bottleneck. IT network specialists would be able to assist with that troubleshooting.