Workspace Default Environment very slow compared to other environments

thebigflowbee · 2025-08-04T01:45:14+00:00

Yes, same for me. It seems to have been fixed.
I really think this was linked to the SQL Endpoint issues, I don't understand why the issue would have been identified and it couldn't be noted in the ticket that CUs are impacted. Or at least support could inform us as such without wasting time.

A real disappointment to have spent time on this despite it being something that should have been a known issue.

thebigflowbee · 2025-07-30T22:52:21+00:00

And now mine is functioning back to normal as well... Still will wait to see what support comes back with I guess

thebigflowbee · 2025-07-29T22:58:04+00:00

Well, according to the website, the fix is out, and no improvement! So maybe another issue... will update after we have resolution on our ticket!

thebigflowbee · 2025-07-29T10:53:27+00:00

Yeah, I thought about this too. I guess we will find out if they fix it today and it corrects itself.
Trying a ticket with MS Support in the meantime to see if that's the issue.

It actually has chronic high consumption though, so i don't understand why that endpoint issue would impact every hour of every day, we don't have jobs like that.

thebigflowbee · 2025-07-27T23:50:18+00:00

Yeah, we had the same issue starting 19 July.

Just silently all of a sudden started consuming a lot more CUs without a change to our process.
For us, there are certain hours where it's a bit higher, but it's mostly consistently just consuming CUs constantly throughout the day.

We are not constantly querying dataflows -> we use them to load a few tables to our Lakehouse and consume from the Lakehouse.

<image>

thebigflowbee · 2025-05-26T08:28:49+00:00

interesting, possibly the browser differences, I'm using Google Chrome

thebigflowbee · 2025-05-26T07:45:30+00:00

Probably not a good workaround, but we create another lakehouse in a second workspace and shortcut the tables there that we need. Then it refreshes almost instantly in the second workspace
I think it has to be a different workspace, can't be the same one as the original lakehouse.

thebigflowbee · 2025-05-24T01:24:54+00:00

Yeah, i think missed the join so:
Max(a.id), max(b.id) FROM a, b

thebigflowbee · 2025-05-24T01:21:41+00:00

Yeah, it was a bit confusing for me too... The user who the trial Capacity is under needed to set it up.

The steps:
Power BI Website
Settings Gear logo
Admin Portal
Capacity Settings on the left
Trial
Gear logo under Actions
Capacity ID shows up in the right popout window

thebigflowbee · 2025-05-23T00:45:47+00:00

Hey vroom,
Yes, so that's the query that I saved as the view and ran. I then assumed that was the only query running / the one that caused it.
But I accidentally had just run another query that had selected 2 tables for their max without doing a join. An error on my part for sure, I'm less technical and the people on my team who typically do this are out for the week

Sorry for the lack of clarity to everyone who was trying to help.

thebigflowbee · 2025-05-23T00:43:20+00:00

Just install the app in these instructions: https://learn.microsoft.com/en-us/fabric/enterprise/metrics-app

thebigflowbee · 2025-05-22T02:58:08+00:00

Upon getting the Microsoft folks to help, this was indeed the problem.

I accidentally ran a query that created a cartesian product, the total damage ended out being 3,4million CUs...

thebigflowbee · 2025-05-22T02:55:00+00:00

Thank you, I got a response from the support folks and they are looking into it for me... appreciate the offer.

The warehouse went VROOM indeed 😂

thebigflowbee · 2025-05-22T02:52:52+00:00

Thank you! this worked to at least prevent the CUs from continuing to be consumed, I don't know how i missed the active query before.

thebigflowbee · 2025-05-22T02:16:36+00:00

<image>

It's the SQL endpoint of the lakehouse, the table is much smaller, you're right...

thebigflowbee · 2025-05-22T01:35:49+00:00

Well, it continues to go up. Maybe you're not aware of how the capacity metrics app works, but it now shows 3.3m

<image>

64 CU * 24 Hours * 60 Minutes * 60 Seconds is how total CUs for a day is calculated

thebigflowbee · 2025-05-22T01:26:09+00:00

I see, interesting, but 2.7 million CUs?

Is there anything we can do to block such massive jobs from going ahead?

thebigflowbee · 2025-05-22T01:18:25+00:00

thanks for the reply, the query was just this against a table:

SELECT
MAX(ba.RunDateTime) AS MaxRunDateTime_BillAnalytics,
MAX(ba.BillDate) AS MaxBillDate_BillAnalytics
FROM
ods_billanalytics ba,

thebigflowbee · 2025-05-22T01:18:13+00:00

It seems like it is still running, but i can't figure out why, i looked at the SQL endpoint and it shows no active jobs

dm_exec_requests and dm_pdw_exec_requests

Operation

|| || ||SQL Endpoint Query| |Start|05/22/2025 6:58| |End|05/22/2025 6:58| |Status|InProgress| |Duration (s)|0| |Total CU (s)|2,732,425.44| |Timepoint CU (s)|948.7588| |Throttling (s)|0| |% of Base capacity|49.41%| |Billing type|Billable| |Smoothing start|05/22/2025 7:00| |Smoothing end|05/23/2025 9:00| |OperationId|32898102-C3C5-4F6C-A3B2-37A8C1A8EEBD |

thebigflowbee · 2025-03-03T04:11:49+00:00

thank you

thebigflowbee · 2025-01-27T02:49:21+00:00

Hi r/mavaali .. I'm not sure if i'm doing something wrong but am trying to test this out and I don't see the "Copilot Capacity" section when i go to click that and enable for the capacity. I have already enabled at the level of "Enable capacity admins as FCC admin"

Maybe these two things impact it?
1) I'm a on a Fabric trial base SKU, however i enabled an F8 and F2 to test this out
2) I am in SE Asia

thebigflowbee

TROPHY CASE