Forum Discussion
• Data Flow - SharePoint Folder Connector REALLY SLOW - Evaluation Cancelled
Hi Anonymous ,
There are many causes lead to slow performance. You are using flat files as datasource, so there isn't query folding in your datasource. The mashup engine needs to load all files at the same time then do transitions, it will lead to large memory use . The complex transition will leads to large cpu use.
Are you using dataflow in premium? You can try to enable Enhanced Dataflows Compute Engine and enlarge the Max Memory in workload. Please refer to https://docs.microsoft.com/en-us/power-bi/transform-model/dataflows/dataflows-premium-workload-configuration
And use computed entity is also a option for you.
Here is a official document for your reference: https://docs.microsoft.com/en-us/power-query/optimize-expanding-table-columns . The expand steps could be the issue of slow performance. when you use join and expand steps, it will increases the number of HTTP calls by one for each row in your datasource.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Best Regards,
Dedmon Dai
Hi Anonymous ,
There are many causes lead to slow performance. You are using flat files as datasource, so there isn't query folding in your datasource. The mashup engine needs to load all files at the same time then do transitions, it will lead to large memory use . The complex transition will leads to large cpu use.
Are you using dataflow in premium? You can try to enable Enhanced Dataflows Compute Engine and enlarge the Max Memory in workload. Please refer to https://docs.microsoft.com/en-us/power-bi/transform-model/dataflows/dataflows-premium-workload-configuration
And use computed entity is also a option for you.
Here is a official document for your reference: https://docs.microsoft.com/en-us/power-query/optimize-expanding-table-columns . The expand steps could be the issue of slow performance. when you use join and expand steps, it will increases the number of HTTP calls by one for each row in your datasource.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Best Regards,
Dedmon Dai
Hello v-deddai1-msft and selimovd , thanks for the reply and support. I found a way to optimize my query, the SharePoint that was hosting my folders and files, was too ''busy'', it was hosting a lot of folders and files...It was taking forever to find the folder to use as dasource. So I created a separate Site to use as repository for flat files, now te performance is better...not super fast, but I can manage. I'll read that documentation regarding expanding and merging queries.
Thanks again both of you for the support!!!