really slow access to PBI semantic model via both reports and excel

[Anonymous]

hi all, 
we are facing with isasues related to acces to our data model ( aka semantic model). 
the story is the following - we have premium capacity P1. and during last two weeks our users are blocked by fabric because of unavailable capacity. 
the strange part of that is I'm a developer of our PBI model and in our capacity we have 1 publushed semantic model, and I'm facing with issues getting acces via Excel during connections ang getting just meta data of our tabular model - I mean that Excel can load just a list measure/dimentions about 3-5 minute. it looks really strange. 

also we have a problem with reports based on our semantic model - a loot of users have 'loading... phrase' and it takes a sagnificant amount of time. 

can you please help us to understang the root of cause? there are no cnahges of th model still september, but I can see that we have unexpected users' experience and cannot understand why it happens. 

please let me what information I can add here to figure out if  it helps. 

BR, 
Val

[Anonymous]

many thanks for ideas, 
MS tech support says that we are affected by new throlling policy - 

Understand your Fabric capacity throttling - Microsoft Fabric | Microsoft Learn

and there are two options here : 
1) autoscale - need to pay additionally at least 85$ per day 
2) or pause-resume capacity - 

Follow below document to pause and resume the capacity:

https://learn.microsoft.com/en-us/fabric/enterprise/pause-resume 

not really sure how the second option will help us - but  the first one is not available for now, because of additional payments.

really bad new that smth was changed and we face with issues. 

[lbendlin]

We had the same situation, but we were able to offload workspaces to different capacities so the throttling was "only"  active until the overage was compensated.  If you only have one capacity then that will have a much larger impact.

"Pause-resume capacity"  That's a joke.  With Gen2 we as the capacity owners no longer can restart capacities!!!

[Anonymous]

many thanks,m 
jokes, yeap 🙂 but it's tech support. 

will try to figure out the heaviest queries . 

BR, 

Val

[Anonymous]

Many thanks for your support, 
the CU usage is about interactive/background work with PBI. I understand that we need to find out users/reports with huge queries. ok, here I understand the logic - a lot of time to load data beacause data is calculating, it takes memory and cu , I see this part. 

teh part being not clear to me -   I get access via Excel and it takes about 3-5 minutes just to load metadata from the datamodel, metadata. and also then to load a list of date from data dimentions can take abour 5-7 minutes. it's not users' case, I do that by meself ( I'm a developer) and don't understan why it works so slow and why it worked better 3 weeks ago. it looks like our capacity doesn't work in appropriative way. 

I've also opened a ticket with microsoft - TrackingID#2311230050000148
no results for now. 

if you have any ideas - plese share me with. It critically effects our bussiness users 😞 

BR, 
Val

[lbendlin]

You must clear your overages. If you have another capacity you can move some of the offending workspaces over to that.

[lbendlin]

What does the Fabric Capacity Metrics app say? Are you being penalized for CU over-usage?

Since you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi

[Anonymous]

Many thanks for your support,
Yes, it says that CU usage is too high, and then it looks like queries are penalized for CU over-usage. The more users, the more usage - I totally agree with this opinion, but we didn't have so many problems and negative from users last month, it happened unexpectedly about 2 weeks ago and we have been getting negative feedback about access to reports/direct usage of PBI model via Excel from users and the count of internal tickets related to PBI is significally growing. will open a pro licence ticket. thanks.
BR, Val

[lbendlin]

The Fabric Capacity Metrics app will list the processes that eat CU the most. Identify the developers behind these processes and work with them to reduce their impact. Fewer refreshes, better data models etc.