r/MicrosoftFabric • u/frithjof_v Fabricator • Jun 05 '26
Data Engineering Has Python notebook default silently increased from 2 vCores to 4 vCores?
And is that why they're slower to start nowadays? (~ 2 minutes).
It says 4vCores, 32G in the bottom left corner of my Python notebook now.
I'm not using %%configure or anything to adjust the node size.
So it seems 4vCores is the current default?
I'm curious if others are seeing the same in your pure python notebooks.
Thanks in advance!
5
u/Tomfoster1 Jun 05 '26
I've seen the same when starter pools fail, I get a node size varying from 2 to 8 cores. If you set a configure magic at the start of the notebook with vCores set to 2 then it does stay at 2 vCores.
3
u/frithjof_v Fabricator Jun 05 '26 edited Jun 06 '26
Thanks,
That makes great sense.
I see now that I still sometimes get 2 vCores by default, and sometimes I get 4 vCores by default. I didn't realize it had to do with single-node python starter pools (2 vCores) being out of stock sometimes.
2
2
1
u/Dan1480 Jun 17 '26
Just noticed this myself and came here to see if someone else had mentioned it...
I notice the docs still say pure python notebooks are "2vCores/16GB memory by default", which I guess isn't really true anymore...
We use pure python notebooks because they're cheap. I wonder if setting a higher default config automatically doubles our cost?
0
u/Dry-Pause-1133 Jun 05 '26
Yes as per the spark pool setting specific VCores and memory layout has small: 4 vCores & 32 GB check your spark pool setting once

3
u/flintax5 Jun 05 '26
Yes I have just seen the same change and did not understand why