Forum Discussion
Refresh data from Log analytics
Hi, I have dataset that uses 6 Log Analytics queries as a data sources.
I guess that's Log Analytics API limitation, but when I'm trying to refresh them all at once it takes a lot and never ends or ends with timeout.
Is there a way to force the refresh to be performed one by one for each query added to a data set?
When I'm refreshing it manually from Desktop it works fine, but when a scheduled refresh is launched from web it crashes after all.
Thanks in advance for any help.
Hi tymb ,
It is not supported to disable parallel loading of tables in the Power BI Service currently .There is an idea about this issue, please vote it up, Need option to disable Parallel loading of tables in PBI Service , to improve the Power BI.
It is a place for customers provide feedback about Microsoft Office products . What’s more, if a feedback is high voted there by other customers, it will be promising that Microsoft Product Team will take it into consideration when designing the next version in the future.
We also submitted this feedback to the product group internally, so that the product group can pay attention to this problem and speed up the issue repairing.
When the refresh is in fact slow or crash, it can be due to several reasons:
- Insufficient CPU (refresh can be very CPU-intensive).
- Insufficient memory, resulting in refresh pausing (which requires the refresh to start over when conditions are favorable to recommence).
- Non-capacity reasons, including data source system responsiveness, network latency, invalid permissions or gateway throughput. You may increase the capacity for workspaces to increase the model refresh parallelism frequency.
- Data volume - a good reason to configure incremental refresh, Incremental refresh can significantly reduce data refresh duration, especially for large model tables. See more: Incremental refresh in Power BI Premium .
See more details: https://docs.microsoft.com/en-us/power-bi/whitepaper-powerbi-premium-deployment#why-are-refreshes-slow.
You can also use some tips to improve the performance:
Enable Row-Level Security (RLS) where applicable.
Use Microsoft AppSource certified custom visuals where applicable.
Do not use hierarchical filters.
Provide data categorization for Power BI reports (HBI, MBI, LBI).
Use the On-premises data gateway instead of Personal Gateway.
Use slicers sparingly.
Remove unused tables or columns, where possible.
For more information on optimizing data sources for DirectQuery, see DirectQuery in SQL Server 2016 Analysis Services.
You can refer to the links to see more performance tips:
https://docs.microsoft.com/en-us/power-bi/power-bi-reports-performance,
https://blog.pragmaticworks.com/power-bi-performance-tips-and-techniques,
https://maqsoftware.com/expertise/powerbi/power-bi-best-practices.
(Please understand that this link is provided “AS IS” with no warranties or guarantees of content changes, and confers no rights.
Best Regards,
Amy
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
1 Reply
Hi tymb ,
It is not supported to disable parallel loading of tables in the Power BI Service currently .There is an idea about this issue, please vote it up, Need option to disable Parallel loading of tables in PBI Service , to improve the Power BI.
It is a place for customers provide feedback about Microsoft Office products . What’s more, if a feedback is high voted there by other customers, it will be promising that Microsoft Product Team will take it into consideration when designing the next version in the future.
We also submitted this feedback to the product group internally, so that the product group can pay attention to this problem and speed up the issue repairing.
When the refresh is in fact slow or crash, it can be due to several reasons:
- Insufficient CPU (refresh can be very CPU-intensive).
- Insufficient memory, resulting in refresh pausing (which requires the refresh to start over when conditions are favorable to recommence).
- Non-capacity reasons, including data source system responsiveness, network latency, invalid permissions or gateway throughput. You may increase the capacity for workspaces to increase the model refresh parallelism frequency.
- Data volume - a good reason to configure incremental refresh, Incremental refresh can significantly reduce data refresh duration, especially for large model tables. See more: Incremental refresh in Power BI Premium .
See more details: https://docs.microsoft.com/en-us/power-bi/whitepaper-powerbi-premium-deployment#why-are-refreshes-slow.
You can also use some tips to improve the performance:
Enable Row-Level Security (RLS) where applicable.
Use Microsoft AppSource certified custom visuals where applicable.
Do not use hierarchical filters.
Provide data categorization for Power BI reports (HBI, MBI, LBI).
Use the On-premises data gateway instead of Personal Gateway.
Use slicers sparingly.
Remove unused tables or columns, where possible.
For more information on optimizing data sources for DirectQuery, see DirectQuery in SQL Server 2016 Analysis Services.
You can refer to the links to see more performance tips:
https://docs.microsoft.com/en-us/power-bi/power-bi-reports-performance,
https://blog.pragmaticworks.com/power-bi-performance-tips-and-techniques,
https://maqsoftware.com/expertise/powerbi/power-bi-best-practices.
(Please understand that this link is provided “AS IS” with no warranties or guarantees of content changes, and confers no rights.
Best Regards,
Amy
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.