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
Ability to Isolate Fabric Workspaces Across Browser Tabs and Windows - Power Bi Service
When opening a Fabric workspace in a new browser tab, I cant keep different workspaces open across multiple tabs. The workspace context appears to be shared between tabs. For example: Tab 1 = Dev...aashraysood58 minutes agoMicrosoft EmployeeNew105Views9likes2CommentsSupport VNet data gateway connections in Power BI Report Builder (Get data / Power Query)
Power BI Report Builder can't use a VNet data gateway connection. In Get data (Power Query), the Data gateway field shows "none" and can't be changed, so the query goes straight to the source over th...ilia_ryzhkov8 hours agoNew MemberNew18Views2likes0CommentsOption to set custom width for gridlines OR fixed outer padding
When designing reports, using the align and distribute evenly options in the format pane are useful, however when designing report pages with fixed bleeds between visuals I have to follow these steps...IolaWhiteley16 hours agoAdvocate IINew6Views0likes0CommentsDefault Scrollable Time-Series Charts to Most Recent Data
Currently, Power BI time-series charts always open scrolled to the earliest (leftmost) date by default, which is inconvenient for reports where users are interested in the most recent (rightmost) dat...CStillwell17 hours agoNew MemberNew23Views2likes1CommentOption to Stop Fabric Planning Billing Session After Plan Item Deletion
Currently, a Fabric Planning session remains active for 30 days once triggered. If a user creates a Plan item only for testing and deletes it the next day, the billing session still continues and c...v-dugumarrir118 hours agoMicrosoft EmployeeNew48Views11likes1Comment