Long Connection Time When Triggering a Notebook in a Pipeline

[ahmetyilmaz]

I'm experiencing an issue with long connection times when triggering a notebook within a pipeline in Microsoft Fabric. When running the notebook normally, the connection time is relatively fast after the initial connection is established. However, when the notebook is triggered through a pipeline, a new connection is established every time, which leads to significantly longer connection times.

I have tried using a session tag, but the connection time has not improved. Is there any way to keep the connection to a notebook always open? Or is there a way for the pipeline to connect to the same notebook connection repeatedly to improve the execution speed?

[lbendlin]

Is there any way to keep the connection to a notebook always open? 

That would be much worse for you as you would pay dearly in CUs for keeping notebook sessions open.

[ahmetyilmaz]

You're right. Do you have any suggestions for a short connection time ?

[lbendlin · Accepted solution]

I don't. I don't want to suggest something that costs you lots of money.

[ahmetyilmaz]

@lbendlin  Hi, do you have a different solution? I still have this problem sometimes. Connection time takes too long.