Forum Discussion

D4zk's avatar
D4zk
Frequent Visitor
1 year ago

Fabric Executor Running Time too long

Hi all, I'm using F4 and run a pipeline that calls some child Fabric notebooks to load data. I'm facing with the execution is too long 7-8 mins. While In my notebook, all cells take total execution ...
General Question
Need Help
Anonymous's avatar
Anonymous
Not applicable
1 year ago

Hi D4zk ,

 

It looks like your pipeline is taking much longer to execute than a single notebook unit.


Are there any other concurrent interactions during the time you are running the pipeline? Make sure these dependencies are not causing delays. Network latency or slow response from external systems can affect the overall execution time.

Alternatively, refer to the following document for a description of the detailed metrics of pipeline operation.

How to monitor pipeline runs - Microsoft Fabric | Microsoft Learn

 

Best Regards,
Adamk Kong

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

D4zk's avatar
D4zk
Frequent Visitor
1 year ago

Hi, I already find an approach to help reduce the time to start, queue and idle of node, that is using DAG to call all notebooks from 1 main notebook. It can help me reduce from 2 hours to 37 minutes for 37 tables.

Thanks for you response.