- Composite model performance consideration means balancing Import and DirectQuery tables in the same model.
- In one project, combining a large sales table in DirectQuery with small dimension tables in Import caused slow visuals.
- DirectQuery queries hit the source every interaction, adding latency.
- Relationships between DirectQuery and Import tables can trigger complex queries.
- Measures involving both modes may increase CPU load and memory usage.
- We optimized by importing frequently used tables and keeping rarely queried tables in DirectQuery.
- Aggregations were created to reduce source hits.
- Overall, careful design ensures responsiveness while leveraging both storage modes efficiently.
What is composite model performance consideration?
Updated on February 25, 2026
< 1 min read
