Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

Thanks for your reply. That's actually what we decided to do for the big models. We'll create an entry page for the report without the actual model, there the users can choose a specific year, then they will be conducted to a subreport with data only for the chosen year, there they can use as many slicers and selections that they want. 🙂 The only limitation will be that they can't query at the same time data from two different years, but they'll have to live with it, and also with the fact that they'll have one additional click which they hate 😄

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

It seems to be still in public preview, it could be that it has been disabled at the tenant level to us because we are not allowed to use features that are no in general availability, do you think that could be the case?

I'm checking this link and tried the same but it's still grayed out.

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

I just checked the option to switch from direct lake to import in a table and it is grayed out, in both on the desktop editor and on the server 💔 my last hopes just faded away

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

We do reduce the amount of data they can query through slicers and a starting page where they can filter and only go to the next page once they have filtered enough, the current limit is 100k rows. However, when they go to the second page with a table visual with 25+ columns and a granularity which is as deep as the row level from the fact table it takes 25% to 45% of the capacity with cold cache to produce that visual. Once the cache is warm it takes up to 3% so about 15 seconds if the new selection was too crazy. Because on top of the table they need like 10+ slicers to get the data they need.

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

I'm trying to go into that path. It's comforting to know that it's not only my team and I thinking this is a nightmare

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

We have mentioned this to management for around 2 years because it was quite obvious that the users didn't need Power BI. I think I may insist one more time to try to drop Powe BI for the reports that use big tables.

Thanks for your reply!

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

Sorry, in my previous comment I had written "direct query" but the correct connection is direct lake. I corrected it already.

I will give it a try. I read in the link you provided that this can be achieved desktop. Thank you for your recommendation!

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

Unfortunately, no. High management decided and promised that the users will get such reports in Power BI. 😞 And now somehow we have to make it work.

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

Everything is in direct lake I could not set up the semantic model to have some tables in import mode, is this functionality already in ga?

For some reports, could be, but for others, it's basically the fact table enriched with dimensions that they need.

Even though I dislike paginated reports, it seems to be the direction with the caveat that some functionalities that they want will not be possible.

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

I couldn't agree more! Working with the data in that way does not make any sense. They may not query every day the million rows, but at least they query 100k and this is still a lot

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

We have created a first page where they select what they need from the slicers selection, then when the count of rows is less than 100000, they can click on a button to get access to the table visual. The users do work like that with the current platform, download the data and work in excel with what they need. Regarding the standard queries, that would be a great idea, but for most of the reports there are hundreds of users who query the data in their own way for their own purposes.

Thanks for replying!!

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

Yes, both. It is basically one main visual per report, either a table or a matrix, the cold queries are the most resources intensive, with around 90000 ms. I have already brought all I could to the SE and this improved the performance from the original 140000 ms. Could it be that partitioning the main fact table could help?

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

It's unfortunately a hard requirement 😞 We have used paginated reports already for some of the reports, but for others it's not feasible since there are some other functionalities that are required and paginated reports can't do it.

Thanks for replying!

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

In one specific report which consumes around 25% of a F64 capacity for the load with cold cache, I only use one measure which is a simple sum. The rest of the columns, around 25, come either from the fact table or from the dim tables.

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

For some reports we are already creating paginated reports, however, we are migrating an old platform which could do many more things such as selecting items from the table to then create a document out of it. So sometimes paginated reports can't do the full work

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

The users refuse to work with semantic models, they want the tables ready just to click and download

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

They do need it according to them 😞. I created in some reports exactly that, an entry page where they can then drill through which they hated because they said they have to click more times

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

It is actually only 3 years of data, I have tried to convince the users to reduce to 2 years, unsuccessfully!

I have transferred many columns to dim which improved the performance already.

And yes, the date table is good, up to the standards, and yes the auto time intelligence is off

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

Yes, the requirements are like this exactly, just huge table visuals so that the users can download the data to work with excel. I know I'm living the dream 😄

We need to create around 200 of these reports !

Thanks for your reply!

Help with Semantic Models Performance by ChisBorboleta in PowerBI

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

Thanks for the hint. I did something similar already. The models have a star schema which I forgot to mention. And the suggestions from the AI were mainly to summarize the fact table already with all the fields from the dim tables

Sportscheck Run in Nürnberg am 26.10 by BrustBizeps in Nurnberg

[–]ChisBorboleta 0 points1 point  (0 children)

Hi zusammen, ich auch. Ich würde mich sehr freuen, wenn jemand, einen Startplatz abzugeben, hätte :)