Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
I work on models that can take from seconds to 5 minutes+ to render from SQL/SSAS but as I will eventually be using a bespoke web interface, I need the queries to be super quick . I keep the visualisations relatively simple.
Now that I am getting into the perforance analyzer / dax studio and power bi aggregations aside, I was just wondering, from your experience, if you have a list of DAX keywords to look out for as you ended up changing/ avoiding them as they are known or likely to be performance killers.
e.g FILTER can be slow.
One other performance improvement I found helpful was to reduce the number of measures a call would have to go through. Although it's helpful to break down logic into multiple measures, there is a performance hit to doing this way since each measure is itself a CALCULATE function.
@Anonymous is 100% correct. If things are slow chances are your data model is not set up correctly for DAX and/or you are writing your DAX measures to be slow (i.e. Using Filter with a Fact Table). When in doubt try to cut down on the cardinality of the columns and keep tables narrow as possible. Everything works better with longer narrow tables vs. wider shorter tables.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
49 | |
26 | |
20 | |
15 | |
12 |
User | Count |
---|---|
57 | |
49 | |
43 | |
19 | |
18 |