Max Parallelism Per Query stopped working?

[jeffshieldsdev]

I've been using this approach for a few weeks of changing Max Parallelism Per Query in a DirectQuery dataset published to a Premium capacity Workspace to have queries execute concurrently instead of consecutively:

DirectQuery parallelism in Power BI (crossjoin.co.uk)

It appears this stopped working recently.

I've tried reapplying the settings with Tabular Editor, and opening in Power BI Desktop, refreshing and republishing to Power BI Service, and reapplying configuration using Tabular Editor:

I'm still seeing a very much waterfall consecutive execution pattern in DAX Studio Server Timings tab:

Is anyone else experiencing the same?

[jeffshieldsdev · Accepted solution]

From Microsoft:

"product team have temporarily disabled parallelism for datasets utilizing aggregations. This decision was made due to internal errors that have risen with these datasets.

I am pleased to inform you that the product team has already fixed this issue. The fix is now (2023-11-09) ready for deployment on a cluster-by-cluster basis."

I have confirmed MaxParallelismPerQuery is being honored again.

[GilbertQ]

Hi @jeffshieldsdev 

I would suggest chatting to your Power BI Admin to see if they have made any changes to the capacity settings?

[jeffshieldsdev]

Thanks for the reply.

I am capacity admin and haven't made any changes.