Cascading parameter in report builder is very slow in service

[Shri]

I am rebuilder a PBI report on report buiders and it requires 6 levels of cascading parameters. Until 2 levels Region - State, the report has no performance issues, however beyond that , Region- State- City, the report is too slow. The DAx queries that I am using , all have used filter function to remove the Blanks/ null values from each of the parameters. Does cascading parameter make report performance slow in Report Builder? How can I improve the performance with cascading parameters? Please help.

[v-shex-msft · Accepted solution]

Hi @Shri,

I think it might be one reason for the performance issue.

For cascading filters, they not only affect themselves but also affect the previous and the next level filters. (these operations will trigger to send queries and update the binding data source for many times and may also iterate trigger the same operations on the next level filters)
If this is a case, it means they will send multiple queries of different filters at the same time to update their items and iterate the next level with the same operations.

Since the next level filter required the previous level selections as the parameter into the sent queries.  These operations weren't able to parallel processing and there will await until the previous operations finished to continue the processes on current and next level filters.

Use cascading parameters in paginated reports#recommendations 

I hope these descriptions can help to clarify your scenarios.

Regards,

Xiaoxin Sheng