Forum Discussion
PC advise Specification for Developing Dashboards for "Big Data" multiple DAX codes
Hi PowerBI_LOVER,
Even if you go for the service the refresh of 100m rows will take longer than 30 minutes specially if you are trying to do a lot of transformations and tables using dax.
If you are trying to load 100m rows to desktop has I referred previously has a best practice you should not do that.
The dax measures have no impact in terms of refresh since they are only calculated at the time you called them on your visuals.
Altough I understand what you want to achieve with this type of configuration large semantic model should be setup with only part of the data and then push the refresh to the service.
On top of this having this large semântica models you also should consider the usage of incremental refresh or aggregation tables, this will reduce the refresh time but also the performance when building your reports.
Hi Miguel Félix,
100 Millions rows with a computer with 32GB of ram and an I7 - If you have only dataset you are viewing maybe.
I have used 32GB on I5 and it can with dataset viewing.
I am taking about 600 lines of dax - measures and table codes.
32GB will refresh for over 30mins.
So my configuration above will work or alternatives to my configuration for large scale Dataset and Multiple Dax codes.
Thanks
Hi PowerBI_LOVER,
Even if you go for the service the refresh of 100m rows will take longer than 30 minutes specially if you are trying to do a lot of transformations and tables using dax.
If you are trying to load 100m rows to desktop has I referred previously has a best practice you should not do that.
The dax measures have no impact in terms of refresh since they are only calculated at the time you called them on your visuals.
Altough I understand what you want to achieve with this type of configuration large semantic model should be setup with only part of the data and then push the refresh to the service.
On top of this having this large semântica models you also should consider the usage of incremental refresh or aggregation tables, this will reduce the refresh time but also the performance when building your reports.