Forum Discussion
DirectQuery report gets slower with time
Hi Svet_Dimov,
Thank you for reaching out to the Microsoft Fabric Forum Community.
Thank you vanessafvg, for providing your insights,
You're right to focus on the growing "Other" time in Performance Analyzer while it's usually tied to synchronization between visuals, in your scenario with Direct Query and auto page refresh, it likely reflects cumulative overhead affecting the entire report.
One possibility is query overlap, where new refresh cycles begin before previous ones complete, especially if the interval is short. Increasing the refresh interval slightly (e.g., from 1s to 5s) may help.
Additionally, the rise in other times may be due to client-side memory buildup, particularly from dynamic elements like multilingual text boxes. Monitoring Power BI Desktop’s memory usage over time using Task Manager could confirm this.
I’d also suggest duplicating your report page and testing a simplified version without text boxes, background images, or buttons compare the two using Performance Analyzer to isolate the impact of visuals.
Lastly, while your back-end tables are small, it’s worth checking with your Databricks admin to ensure sessions aren’t being repeatedly reinitialized or queued, as that could also contribute to latency. Hope this helps narrow down the issue. Feel free to share your findings.If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
The report page is quite simple. It consists of the following:
1 table visual with 8 columns. They all come from the same Azure Databricks connection. The SQL for the connection is also very simple select of fields from two joined small streaming tables (inner join 1-1 relationship).
1 background image
8 text boxes/buttons with dynamic text (DAX measures that translate the report in two languages)
2 buttons with Web URLs.
No slicers are present in the page and no filters are applied anywhere. That's what makes things so confusing...
Hi Svet_Dimov,
Thank you for reaching out to the Microsoft Fabric Forum Community.
Thank you vanessafvg, for providing your insights,
You're right to focus on the growing "Other" time in Performance Analyzer while it's usually tied to synchronization between visuals, in your scenario with Direct Query and auto page refresh, it likely reflects cumulative overhead affecting the entire report.
One possibility is query overlap, where new refresh cycles begin before previous ones complete, especially if the interval is short. Increasing the refresh interval slightly (e.g., from 1s to 5s) may help.
Additionally, the rise in other times may be due to client-side memory buildup, particularly from dynamic elements like multilingual text boxes. Monitoring Power BI Desktop’s memory usage over time using Task Manager could confirm this.
I’d also suggest duplicating your report page and testing a simplified version without text boxes, background images, or buttons compare the two using Performance Analyzer to isolate the impact of visuals.
Lastly, while your back-end tables are small, it’s worth checking with your Databricks admin to ensure sessions aren’t being repeatedly reinitialized or queued, as that could also contribute to latency. Hope this helps narrow down the issue. Feel free to share your findings.
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you.