Forum Discussion

PowerBI_LOVER's avatar
PowerBI_LOVER
New Member
1 year ago
Solved

PC advise Specification for Developing Dashboards for "Big Data" multiple DAX codes

When working with advanced DAX codes in tools like Power BI, a high-performance machine is crucial for smooth data processing and report development. Here's an updated list of ideal PC specs for deve...
Need Help
  • MFelix's avatar
    MFelix
    1 year ago

    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. 

v-pnaroju-msft's avatar
v-pnaroju-msft
Community Support
1 year ago

Hi PowerBI_LOVER,

We sincerely appreciate you for taking the time to share such detailed specifications and insights with the Microsoft Fabric Community. Contributions like yours are immensely valuable in assisting fellow users to comprehend and evaluate the hardware requirements for large-scale Power BI and DAX-based development environments.

We would also like to extend our gratitude to MFelix for your thoughtful and experience-based response. Your valuable insights on model optimisation, performance strategies, and the significance of DAX in enhancing report responsiveness greatly enrich this discussion.

Thank you.