Forum Discussion
Fastest possible access time for power platform dataflows? Gen2 DF in 2024
Hi dbeavon3
While I can understand it feels like 10 seconds is a long time, you have to understand that even though you are using premium capacity, it still requires time to get the resources to then process what you need to be done.
GilbertQ
If I had told you it took 60 seconds to retrieve a single 1KB row of data, would you have believed me? Or 600 seconds? I think 10 seconds overhead per table is crazy, and is hard to find a way to short-circuit that. Ideally there would be a "mock fabric" or "sync fabric" or something else that we could run locally on the desktop (something incredibly fast, instead of incredibly slow).
Do you know if there is any way to dig into these delays to isolate where they are coming from? Another thing I noticed is that the delays are far longer (eg. an additional ~10 seconds) when refreshing the final dataset, than they are when interacting with the gen2 dataflow in the "transform/editing" window.I'm guessing there are some workarounds, assuming I can isolate the source of the delays. Perhaps workarounds are avaialble without even needing to leaving Fabric.
... But as a last resort, customers might consider sending the results of our dataflows to an independent ADLS storage account, for the sake of fast and reliable retrieval:
By setting some portions of Fabric aside, I'm certain that I can get predictable performance behavior by ingesting from a normal ADLS storage account.
