Forum Discussion
Improve report/dashboard performance and loading speed
Hi mdm2025 ,
It sounds like you’ve built quite a substantial report, and it’s easy to see why performance might be struggling a bit given the amount of data and complexity involved. Before going down the route of splitting the report, it’s really worth focusing on optimizing the model and DAX first, since that’s usually where the biggest improvements come from. If your survey data is set up with one column per question, try restructuring it so each row represents a single response to a question. That approach tends to compress much better in Power BI and makes calculations more efficient. It also helps to remove any unused columns and double-check that your data types and relationships are as lean as possible, ideally following a clean star schema.
On the DAX side, review the measures that are doing the heavy lifting and see if they can be simplified or rewritten using variables to avoid repeated calculations. Creating base measures that other measures can build on can also make a noticeable difference. You might also want to check which visuals are taking longest to render by using the Performance Analyzer in Desktop sometimes a few visuals or interactions are the main cause of the lag.
The difference you’re seeing between Desktop and the Service is fairly normal with larger models, since the Service is running on more powerful infrastructure. For development, it can help to work with a smaller sample of your data and turn off background data or auto-refresh while you make changes.
If, after optimization, it still feels too slow, then splitting it into smaller, focused reports is a perfectly valid approach. Just be sure to keep a single shared dataset in the Service so your DAX and data model stay centralized. That way you can manage everything in one place while giving users faster, lighter reports to work with.
In most cases, though, a round of careful model and DAX tuning will give you a noticeable boost before you need to consider breaking it apart.
Best Regards,
Tejaswi.
Community Support
Hi mdm2025
Its a very Genric Question in Power BI Interviews as well regarding this Optimization. The best Way I would suggets is that create a Data Model and Measures in a single power Bi File and Publish it into service without any visuals in it.
Then Open a new Power BI file and load data using the Power Bi Semantic Model or Power Bi Datasets Option and follows the below steps:
Step 1: Publish your main dataset
Keep your existing .pbix file with data model + measures only (no visuals).
Publish this to the Power BI Service as your Certified Semantic Model (say, SurveyAnalyticsDataset).
Step 2: Create “thin reports”
Open a new Power BI file → Get Data → Power BI Datasets → connect to your published dataset.
Build each new report with only the required visuals (2–3 pages per report).
Keep related measures and field parameters grouped logically (e.g. “Engagement”, “Satisfaction”, “Demographics”, etc.).
These thin reports load instantly in Desktop because they don’t contain the heavy model.
Step 3: Create a central dashboard or Power BI App
In Power BI Service, create a dashboard or App that links to these reports.
Your existing landing page can become the Dashboard Home with tiles or buttons linking to each smaller report.
This achieves:
✅ Faster development
✅ Easier testing and maintenance
✅ Reuse of the same data model (no duplication)
✅ Better governance (centralized dataset)
Hope this Helps!