Forum Discussion
New Deployment Pipeline - long delay to show changes between workspaces
Hi,
For a while now the NEW Deployment Pipeline takes a very long time (sometimes multiple page refreshes) before it shows the differences between workspaces for us. This workspace is relatively heavy with many dataflows, semantic models and reports. Did anyone experience something similar with a loaded workspace?
It is quite anyoing and delays the deployment a lot, instead of a few minutes it can take easily 10-15 minutes. 😕
Any advice is appreciated or maybe MS can fix it soon.
Thanks.
BR
Daniel
8 Replies
- v-sgandrathi
Community Support
Hi Danalber,
Here are some steps you can try:
Clearing your browser cache and cookies might sound like basic advice, but it's genuinely helped us fix performance lags, especially after recent Power BI UI changes.
Using the latest version of a Chromium browser like Edge or Chrome makes a real difference. We noticed that Firefox or older versions of Chrome tend to be slower during comparisons.
Keeping the number of open tabs and background processes low also helps. Power BI can be pretty resource-intensive, and having too many heavy tabs open can impact how quickly changes show up.
After deploying, it's worth waiting a couple of minutes before hitting Compare. In our experience, the backend sometimes needs a bit of time to sync everything, especially in larger workspaces.
If your workspace has very large reports or models, consider splitting them across smaller workspaces where possible. This has noticeably improved responsiveness during comparisons.
Thank you and continue using Microsoft Fabric Community Forum.
- Danalber
Advocate II
Thanks v-sgandrathi for your tips.
I'll try to play around with it and see if that will improve the performance. Moving to a different workspace wouldn't be so easy unfortunately.
BR- v-sgandrathi
Community Support
Hi Danalber,
Thak you for letting us know
We wanted to follow up now as we haven't heard back from you regarding our last response. We hope your issue has been resolved.
Thank you for being a valued member of the Microsoft Fabric Community Forum!
- Danalber
Advocate II
Hi v-sgandrathi ,
sorry for the late response.
I tried almost everything you mentioned, splitting up into more workspaces isnt so easy and would required a major requild. It seems the biggest problem is the amount of flows and datasets, just takes a long time to compare. Seems I just have to be patient. 🙂 Just makes it so much harder to deploy because it takes sooo long.Maybe an option to preselect the items which should be deployed would be good, since I know what I updated. Then there is no need to compare the whole workspace everytime.
Cheers
BR Daniel
- v-sgandrathi
Community Support
Hi Danalber,
Thank you for your response. We understand that deployment comparisons can be time-consuming with larger workspaces containing multiple dataflows and datasets.
Your suggestion to preselect items for deployment is appreciated.
Although this feature is not currently available in Deployment Pipelines, we encourage you to post it in the Fabric Ideas Forum so the product team and community can review and upvote it. For now, larger workspaces may take longer, but your input helps us improve.
Fabric Ideas - Microsoft Fabric CommunityWe value your participation in the Microsoft Fabric Community and thank you for your input.
- Tommy-400New Member
I am very sorry to say that Fabric is the worst product ever built by Microsoft. It lacks maturity