Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!View all the Fabric Data Days sessions on demand. View schedule
Hi everyone...
I do hope this is the right place to post this question.
If I create a new Fabric Notebook with nothing in it, and I click Start Session (i.e. for a Standard session) - the session is ready very quickly... something like less than 30 seconds.
If I use my Public Library - where I have a single library included - semantic_link_labs - the version doesn't matter, and I've not changed any other settings... the start up time for the session can exceed 5 minutes. (or at least it has previously and today it's started quite quickly)
The workspace in which this is running is assigned to a F64 capacity - which is less than 20 utilised at the best of times.
Where is the right place to ask questions about this and find information on what is going on and best practice.
- David
Solved! Go to Solution.
Hi @dgwilson, for more explanation about the default starter pools @tayloramy mentioned and expected startup times for various scenarios when using custom environments, check the page What is Apache Spark compute in Microsoft Fabric?.
Hope this helps. If so, please give a Kudos 👍 or mark as Accepted Solution ✔️.
Hi @dgwilson, for more explanation about the default starter pools @tayloramy mentioned and expected startup times for various scenarios when using custom environments, check the page What is Apache Spark compute in Microsoft Fabric?.
Hope this helps. If so, please give a Kudos 👍 or mark as Accepted Solution ✔️.
Good explanation. Thank you.
Hi @dgwilson,
Happy to help.
If I answered your question, please mark the post as the answer to help future forum members find it.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Hi @dgwilson,
THis is expected behaviour.
The default spark pool is always warm, Fabric keeps it running so you cna quickly connect to it.
As soon as you have a custom pool (which your enviornment with a custom library makes) then it is a cold start and Fabric needs to spin up the new pool and get spark running.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Check out the November 2025 Fabric update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!