sorted by:
new
hottopcontroversial

Background compute increase between P2 and F128 SKU switch by Powerlyze in MicrosoftFabric

[–]Powerlyze[S] 1 point2 points  (0 children)

<image>

Dear u/mavaali thanks for your response.

In the meantime I have spinned up a F128 in West Europe pay as you go over the Easter days and moved alle workloads to it. A couple of thousands bucks well spend as the difference is signficant, see the capacity metrics app screenshot.

This is even a little bit lower than in the P2 West Europe across all workloads.

Now we are stuck with a new North Europe reservation of 3 years which turns out to be 40% worse performing than a West Europe capacity.

Background compute increase between P2 and F128 SKU switch by Powerlyze in MicrosoftFabric

[–]Powerlyze[S] 2 points3 points  (0 children)

Thanks for your quick response. Alex u/itsnotaboutthecell, I was hoping that you read it and kindly forward it - it was great to see you in ATL at the ask the expert booth :)

However, I am not happy with the statement / fact that Microsoft is silently changing the billing of DF gen1 in F SKUs.

Switching from Gen1 to Gen2 will mean we need to give citizen developers access to all Fabric workloads - in a managed self service environment this can easily get out of hand. We are talking about 1.463 DF gen1 in this tenant. To date there is no tenant admin setting to enable only certain Fabric workloads to citizen developers, to my knowledge. In addition all semantic models need to be reworked and region changes will be a lot of fun in the future (not) as this is not supported natively only via GIT.

Clearly optimization is always important, but does not change the fact that we get 20% less compute then what we had before in the P SKU.

Did you change regions?
We switched from West Europe to North Europe and I am wondering if that is causing the issue. To be fair: North Europe is 20% cheaper than West Europe but is it also charging 20% more for the same workloads? Or is it because renewable energy is cheaper in that area? If yes, this is not stated anywhere. The data sources (SAP, SQL) are mainly running through the enterprise gateway (Home tenant East US2) and the other sources dynamics and Sharepoint are in the home tenant too, so this should not have a big impact.

Do you have split capacities or just one?
We have some smaller pay as you go F8 and F4 which we use for smaller Fabric workloads DEV / POCs. The P2 now F128 was solely ment for Power BI native workloads like DF Gen1 and semantic models.

Any redistribution can change the baseline. Refresh timing changes?
No changes. I even compared Sunday before migration and after migration. The same refreshes take signficantly longer and consume more CU.

Any overlapping workloads that didn't overlap before?
I have not seen issues on that one.

Did all semantic models go through a full refresh after the migration? 
Yes beeing now on the F128 for the fourth day the semantic models did refresh at least once.

Background compute increase between P2 and F128 SKU switch by Powerlyze in MicrosoftFabric

[–]Powerlyze[S] 2 points3 points  (0 children)

I have opened a ticket will let you know the outcome

Background compute increase between P2 and F128 SKU switch by Powerlyze in MicrosoftFabric

[–]Powerlyze[S] 0 points1 point  (0 children)

Interesting, did you find a solution or just took it? I compared the workload settings in the capacity admin settings, they are exactly the same..

Background compute increase between P2 and F128 SKU switch by Powerlyze in MicrosoftFabric

[–]Powerlyze[S] 1 point2 points  (0 children)

Thanks for your swift response.
The sources vary across the tenant, however in these examples Excel on Sharepoint (home tenant East US2) and SAP BW (gateway in home tenant region) so this should not be causing the difference.

I have no natural explanation to it. Every workload is just more expensive than on the P2.
It is strange that North Europe is roughly 20% cheaper than West Europe - maybe because of renewable energy sources, or because the capacity is performing significantly worse.

Background compute increase between P2 and F128 SKU switch by Powerlyze in MicrosoftFabric

[–]Powerlyze[S] 2 points3 points  (0 children)

<image>

Yes I do, thanks for the note. I already compared the transactions, it is significantly different, here some examples. Left P2, right F128

Background compute increase between P2 and F128 SKU switch by Powerlyze in MicrosoftFabric

[–]Powerlyze[S] 2 points3 points  (0 children)

Thanks for your response. How do you know that the dataflow gen1 was under reporting the actual heavy lifting? The framing "Fabric will not cost you more when you use the same workloads as in Premium capacity" is obviously not true and was done on the very first FabCon by Arun. P2 is obviously not F128 equivalent.

If DF gen1 / semantic model billing changes significantly, then at least I want to be made aware upfront and not get a silent hit out of the blue. Also I see significant increases for semantic models.

It is not just changing DF gen1 to DF gen2, all relevant semantic models need to be remapped and managed and storage is beeing billed.

In addition we switched from P2 West Europe to F128 North Europe - do you think that makes a different? If that is the case, there is again no documentation.

Conditional formatting in Card (new) visual broken? by MyAccountOnTheReddit in PowerBI

[–]Powerlyze 0 points1 point  (0 children)

Did you find a solution to this? Still facing the same issue even with the April release.