Forum Discussion
Slow starter pool session initialization
Hi Anonymous ,
No not yet. We have a deployment freeze in December and this is still being worked on. Team is targeting by Q1 for this to be rolled out to all prod regions. Will update this thread once the support for smaller capacities is enabled.
Which capacities are affected by this issue right now beyond F2 and F4?
I spoke with support yesterday and they claimed that 3 to 4 minutes to start running a notebook is normal... And then when I was demonstrating the start of a notebook it simply failed... 😀
F8 appears to be affected as well
Hey there. I'm still having this issue with slow start ups. I notice that this problem doesn't occur when starting a notebook with the starter pool (which fires up within seconds). So if the starter pool can start up that quickly, it doesn't make sense for a custom pool to take much longer, yeah? Imagine the same notebook being used in parallel and each of them taking that many minutes and times that by the number of jobs in the queue waiting to go through the notebook start up wait time...
Yeah, it is furstrating that they can take several minutes to start up.
One option is to use runMultiple to execute your notebooks. You can define the dependencies and then execute all of the notebooks on a single compute. It only has to start up once rather than for each notebook.
Using runMultiple To Orchastrate Notebook Execution in Microsoft Fabric
