Forum Discussion
DataflowGen2 Slow Performance during design is HORRIBLE
Hi ToddChitt,
I apologize for any inconvenience. Here are the two documents that explain Trail vs Premium. Please review the links below for a better understanding:
Trial Capacity (F64)- Typically time-limited (e.g., 60 days).
- May have restrictions or limitations compared to a paid capacity.
- Designed for evaluation purposes.
Purchased F64 Capacity
- A fully paid, production-ready capacity.
- Includes service level agreements (SLAs) and comprehensive support.
- Ensures uninterrupted access as long as the subscription remains active.
While both options provide comparable compute power, please note that the trial version is temporary and may have certain limitations compared to the purchased capacity.
Please refer to the below links for better understanding:
Fabric trial capacity - Microsoft Fabric | Microsoft Learn
What is Power BI Premium? - Power BI | Microsoft LearnAlso, kindly refer the below link for more information:
Microsoft Fabric concepts - Microsoft Fabric | Microsoft Learn
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
Thanks for your reply. I am EXTREMELY curious about your statement: A Trial Capacity (at F64) and a purchased F64 Capacity are not the same. Do you have documentation to this fact? To be honest, it feels a little like dishonest advertising on the part of Microsoft to promise and F64 Capacity during the Free Trail, but not really deliver it.
Everything I have read, like this from MS: Microsoft Fabric concepts - Microsoft Fabric | Microsoft Learn says that it is the same. Please provide something to refute this.
Regarding the main issue: I did a side-by-side test with another workspace in a different tenant, also under Trial Capacity. For that, I was able to navigate the Excel file and the Lakehouse destination options just fine. During that development time, the original development efforts were hung up on simply navigating the list of Lakehouses available for a Destination. A second paralell test of the same functionality in a new Workspace in the SAME tenant tenant also produced good results. CONCLUSION: The Workspace is at fault. Side note on this Workspace: Every time I went to create a new Dataflow Gen2, it showed up like this:
("Enable Git integration option CHECKED, AND locked out.) To get around it, I always have to switch to a different Workspace in the same tenant, then back again and then I get this (which is what I want)
Those two items together lead me to believe there is something seriously wrong with the Workspace.
My response: Create a new Workspace and move on. I'm not that far into the development work that this is a major effort.
Hi ToddChitt,
After thoroughly reviewing the details you provided, I have identified alternative workarounds that may help resolve the issue. Please follow these steps:
Although Git integration is locked, please create a new workspace without it and check if it functions properly. An admin should review the settings in the Fabric Admin Portal > Workspaces and compare them with a functional workspace.
Remove stored credentials by navigating to Fabric Home > Settings > Data Sources. Delete any existing credentials for SharePoint, Lakehouse, and Warehouse, then re-authenticate. Reconnect Data Sources by manually adding SharePoint, Lakehouse, and Warehouse connections again and verifying if they work.
In the Fabric Admin Portal > Capacity Metrics, check CPU and Memory Usage during periods of slow performance. If high usage is detected, schedule Dataflow work during low-usage hours.
If the issue persists after attempting all the workarounds, please consider raising a Microsoft support ticket. You can create a support ticket using the following link:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
Hi ToddChitt,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi ToddChitt,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.I did some testing:
First, a parallel test of the one workspace against another tenant: same operation(s). The other tenant performed just fine. Second, I created a new Workspace in the same tenant (and under the same Trial Capacity) and THAT worked fine. My conculsion is that there was something about the workspace.
Since I was very early on in the development process, I simply recreated the artifacts in the new workspace and have now deleted the one that was having performance issues.
We meay never know what the cause of the slow performance was. As I said, the issues came around some very basic operations, like while setting up a Dataflow Gen2 destination, it would take 10 minutes to 'browse' the list of available lakehouses.
But now I am EXTREMELY curous about your statement:
- Yes, that’s correct. A Trial Capacity (at F64) and a purchased F64 Capacity are not the same.
Everything I read from Microsoft documentation says that a Free Trial is the same as an F64 Capacty, just that you don't have to pay for it. Please provide documentation to support your statement.