Forum Discussion
Why is there CU usage while no activity running?
for info.
I increased my capacity to see how fast the system can recover.
there was a drop just after this change in capacity, but not enough to make the environment useable again.
there is still a plenty of CU to burn down for no reason.
I finally pause my Fabric Capacity.
I got a spike of 112 000 CUs (or about 101 000% of CU usage)
Then I restart my capacity and everything was back to the normal. no more CU consumed for no reason.
and finally I run a simple pipeline which took 5min to copy some data.
and boom, again I have a constant CU usage of 31% !!!! (1h after I ran the pipeline and everything is IDLE)
the capacity metric report is definitly broken or the CU evaluation is broken.
I no longer have processes consuming my capacity for no reason.
- v-cboorla-msft2 years ago
Microsoft Employee
Hi Jerome22
Thanks for using Microsoft Fabric Community.
Apologize for the issue you are facing. The best course of action is to open a support ticket and have our support team take a closer look at it.
Please reach out to our support team so they can do a more thorough investigation on why this it is happening: Microsoft Fabric Support and Status | Microsoft Fabric
After creating a Support ticket please provide the ticket number as it would help us to track for more information.
Meanwhile you can try the below steps that might help you.
Temporary Glitch: Clearing cookies and caches can sometimes resolve temporary glitches within the application that might be causing the issue.
Corrupted Data: In rare cases, corrupted data stored in the browser's cache related to Microsoft Fabric might be causing the issue. Clearing the cache removes this potentially problematic data.
Hard Refresh: A hard refresh bypasses the cached version of the webpage and forces the browser to download the latest version from the server. Press Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac).
I hope this information helps.
Thank you.
- Jerome222 years ago
Resolver I
Hi,
For info, the dev teams is still not able to solve the issue after 3 weeks.
we also found that the price we are paying is more than the capacity we setup!
for now we are in F2 (plan to upgrade later with an agreement when the problem will be solved) but paying up to 50% more some days! (23 CAD$ instead of 13$)
I start to be very worried about the capacity of your teams to support Fabric. if the devs are not able to find the root cause for something like this, this means the product has a lot (too much) issues to solve everywhere else.
- LukeHRP8 months agoNew Member
It's becoming apparent to me that behind the marketing hype, fabric is a bit of a disaster zone
- Jerome222 years ago
Resolver I
I opened a ticket 2406170040005044
finally I found that ALL the background jobs are all using CU and never really stopped.
I got spikes to more than 100 000 background operations!!!! for no reason
I just reached my 100% CU usage consumed by terminated background executions. this number is increasing and never decreasing.
because I reached 100% of CU consumed by background tasks, I can't burndown my standard activities anymore and my capacity usage % will increase until I pause the capacity.
there is defintly something wrong on the MS side there.
I sent the screenshots and informations to the support team.
- LukeHRP8 months agoNew Member
TBH, I think the best course of action is for you guys to be more clear and honest with your customers. Your marketing definitely does not mention anything about the completely opaque system processes or all the hidden costs and pitfalls associated with Fabric.
Yeah, great you have all your data engineering all under one roof but if trying to develop & run lightweight, minimal processes causes reports to fail for over an hour, then it kind of defeats the object.
My advice is if you have less < 100 users, just use individual power bi licensing and do your data processing outside of Fabric the old school way.
How incredibly disappointing and to suggest contacting support (WQhich we all know is a waste of time and effort) is insulting.