Slow Overwrite Publishing to the PBI Service

Hi Anonymous ,

I don't think it is related to the size of the dataset, as you suggested.  As I mentioned, when dataset/report does not exist, the publish to the service is quick.  The dataset size is normally minimal. (under 100 MB).

Do you seriously believe it is worthwhile to test the roll back to an older version of PBI?  Even if that would make things faster, what would we do with the information?  Where would that take us?

I suspect that this is buggy behavior in the way that the overwrite publishing is implemented.  It probably has to do with obtaining some sort of resource lock, or re-establishing permissions, or re-establishing the gateway setup, or re-verifying the organizational account, or some other uninteresting internal plumbing.

... If there is no "obvious" reason for a long delay, then it seems that the Power BI support team should attempt to look into this.  IE. if the initial dataset publish operation took about 10 seconds, but overwrite publishing takes 5 minutes, then you would think this would indicate a problem.  Would you agree that it is worth opening a support ticket?  How likely is it that the product team would care about a 5 minute delay, with no obvious explanation?  Are these types of quality issues likely to be fixed these days, assuming we can find the root cause?

Please let me know.

Thanks, David