Forum Discussion
Dataset refresh too long (Sometimes)
I am less concerned with the jump in refresh time from an hour + to 4 hours + than I am with the refresh even taking an hour +. Even the largest and most complex semantic models I have come across rarely take longer than 20 minutes. I had a client a few years ago in the Health Care sector that had a bloated 6GB model that was highly inefficient, and it never even took 40 minutes.
My first suggestion would be to look at your query design. Avoid a lot of heavy transformations. If you can set up your queries as dataflows and then ingest the data flows into your model so you are segregating the ETL from the model refresh and you can isolate inefficient queries.
Check your report settings to make sure that parallel loading of tables is enabled.
Hi MikolajSikorsk It may be because of many reasons such as
- High Load on Data Sources: Databases might have more queries on Mondays.
- Gateway Bottlenecks: Resource contention on the on-premises gateway.
- Complex Queries: Heavy transformations or non-folding queries.
- Network Latency: Increased congestion affecting data transfer.
- Overlapping Schedules: Multiple refreshes running at the same time.
For detailed performance check you could check for Gateway Performance and Query Performace follow below for these Monitor Gateway Performance
- Go to Manage Gateways in Power BI Service and check for performance issues or resource constraints.
- Look for logs to identify bottlenecks or unusual delays.
Check Query Performance
- Use Query Diagnostics in Power Query to analyze how long individual steps take.
- Look for long-running steps or queries, especially on Mondays.
If this post helped please do give a kudos and accept this as a solution
Thanks In Advance
Sorry, I have to say it - if I wanted to ask Chat GPT, I would ask Chat GPT...