Forum Discussion
Resolver IIISchedule vs Manual Refresh !!
Super UserHi SpiroswayGR ,
I am happy to try and help but when you reply to your own message with another request that tends to have people skip the reply function since they think it is already replied to and has been resolved.
That said, there are MANY reasons why this can take longer.
To set expectations, Microsoft states that while the system tries to refresh at the requested time, it may be delayed for internal reasons (queues, resource allocation, etc). That could be part of the delay.
Another delay could be if you are using a gateway and have some sort of internal network (or internet) issues (security, too much traffic , etc) that slows the ability of the refresh to be effective.
Also, the queries themselves could be written in such a way that it takes a long time to refresh (the service refresh and the desktop refresh use different engines and react differently so it is quite reasonable that a desktop refresh is fast and a service refresh is slow).
It also could be that when you manually hit the refresh button, there is less concurrent requests. For example, if you have 10 of your reports all set to refresh at 0900 then you are creating your own backup as all of those are potentially hitting the same datasource (may or may not be the same dataset) and that will cause delays.
Resolver IIITo be honest isn't resolved yet and already made a ticket for this one.
I can accept a small delay due the shared server but it isn't so logical to me when i hit "refresh now" to be 4 times faster than schedule.
I am comparing "Refresh now" in powerbi service and schedule refresh in powerbi service too and not powerbi desktop that ofcourse is much faster around.
Furthermore, i am running just one report at same time so it wont be any delay from different reports and as about my capacity i have around 200 mbit and the max used was around 30mbit.
Thank you very much for your time and detail explainations/comments.
Hi SpiroswayGR
You may refer to this blog: Scheduled refreshes are slow, manual refresh is quick
Reason:
Based on my research, The reason scheduled refresh takes longer is because PBI smooths scheduled refresh so AS Engine and Gateway is not flooded with request. PBI doesn't do smoothing for on-demand refresh.
Such as if you set scheduled refresh at 9:00 am, it may start at 9:14 am, and end in 9:16 am, so seems it refresh 10 - 15 min, but if execute an on-demand refresh at 9:00 am, it will start right now and may end in only few minutes. This document also mentioned :
Note also that the configured refresh time might not be the exact time when Power BI starts the next scheduled process. Power BI starts scheduled refreshes on a best effort basis. The target is to initiate the refresh within 15 minutes of the scheduled time slot, but a delay of up to one hour can occur if the service can't allocate the required resources sooner.
If you needs the report be ready by certain time, schedule the refresh ahead of the time or execute on-demand refresh.
Best Regards,
Rico Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- SpiroswayGR
Anonymous
We can understand that we can have a small delay but 15 more minutes is "big fail" for us cause we have also jobs in our servers to run so that cause deadlocks if time will surpass 20-25 minutes.
We are checking this our with Microsoft support through gateway logs and i might come back soon with news.