Python notebooks should have higher concurrency limits than spark notebooks
Currently python notebooks are subject to the same limits as spark notebooks
Concurrency limits and queueing in Apache Spark for Fabric - Microsoft Fabric | Microsoft Learn
From my experiance this means that on an F2 you can not run more than 4 notebook sessions at once via a pipeline. This limit is fine for spark given the higher node size floor meaning that four sessions will likley consume 100% of an F2. However, as python notebooks run by default with 2 vCores you can run far more sessions at once for the same capacity. This limits how many jobs can run at once increasing ETL durations.
Ideally the queue limit for python notebooks should be double the spark notebook queue. E.g. 8 on an F2, or this could be a blended limit, e.g 2 spark notebooks and 4 python notebooks.
Recent ideas
SQL Analytics Endpoint host name - CNAME or defined alias
The host name for a SQL Analytics endpoint is ugly. They look like this: random_ugly_alphanumeric-random_ugly_alphanumeric.datawarehouse.fabric.microsoft.com The first segment looks like it...Mike_Diehl1 hour agoNew MemberNew27Views2likes1CommentFix links generated in multi tenant setups
When I log into Fabric, and I have access to multiple tenants, the links generated for things like monitoring URLs in pipeline runs do not include "ctid=<tenantguid>" query string value, which appear...jwisemanfs3 hours agoNew MemberNew3Views0likes0Comments