My dashboard is slow
First, you’ll want to make sure your browser is on friendly terms with Metabase:
- Clear your browser cache and disable all extensions before refreshing the page, or
- Try loading the dashboard in a private/incognito session.
Dashboard has over 10 cards
- Create a new dashboard for each group of cards that are related to the same time period or segment.
- For example, create new dashboards for weekly vs. monthly metrics, or new vs. returning customers.
- Move your cards to the new dashboard(s) until each dashboard has 10 or fewer cards.
- Use custom destinations to link related cards on different dashboards.
A dashboard with 50 cards is almost always going to be slower than 5 dashboards with 10 cards. Metabase displays a dashboard by refreshing all of the questions on it (that is, re-executing all of the queries against your database). Your data warehouse may try to run these queries at the same time to return the results faster, however, these queries can actually compete with each other and slow things down (like having too many programs open on your computer at once).
Aside from running faster, a small and focused dashboard is also easier for people to understand without getting overwhelmed. For more tips, check out our article on BI dashboard best practices.
Dashboard used by many people at the same time
- Optional: use Metabase’s auditing tools to look at your Metabase usage stats*.
- Set up caching for the questions on your popular dashboard.
- Run the dashboard during off-hours so that people can load the cached results in seconds instead of executing a fresh query to your database.
* Available on paid plans.
If you have a dashboard that many people check around the same time (e.g., at the start of the work day), you may end up with queued queries or saturated database connections. Caching allows you to prepare for peak traffic by running those slow queries once, ahead of time, so that the results are ready to go.
Caching takes less effort because it doesn’t involve any changes to your schemas or databases. If you’re ready to invest more resources into the root cause of dashboard performance issues, check out this list of common schema and database optimizations.
Embedded dashboard is slow compared to original dashboard
- To speed up the embedded dashboard, set up a locked parameter to pre-filter your data.
One of the easiest ways to make a question or dashboard run faster is to work with a smaller dataset. Your Metabase admin can apply automatic data limitations using things like SSO, data permissions, and data sandboxing.
When someone loads a question or a dashboard in a signed embed, however, that question or dashboard will query the full dataset (rather than a smaller dataset limited by permissions). Standalone, signed embeds don’t require people to be logged in, and unauthenticated people viewing the signed embed won’t be subject to the permissions and data restrictions set up by your admin.
Dashboard is slow compared to similar dashboards
- Remove fields (columns) that you don’t need in the final result.
- Add a filter to reduce the amount of data being queried. For example:
- Narrow down the time frame to the reporting period that you care about.
- Exclude invalid records, such as: blanks, nulls, or rows with values like “cancelled”, “expired”, “invalid”, and so on.
- Remove joins to tables that aren’t being used.
- If you’re aggregating data from the query builder, ask your database admin if there’s a pre-aggregated view that you can use instead.
When you update your question to use a minimal number of rows or columns (or switch your question to use a smaller table, such as a summary table) your database can spend less time scanning those records in order to return your results. Narrowing the scope of your question is especially important to think about if you’re starting from someone else’s saved question or model, because you might not need all of the data that the original creator decided to include.
If all of your dashboards are slow, you might be limited by the performance of a particular data source. In that case, we recommend teaming up with your database admin to Troubleshoot database performance.
- Error message: your question took too long.
- Questions that use numbers, dates, or times are slower than other questions.
- I can’t save my question or dashboard.
- I can’t view or edit a question or dashboard.
- My visualizations are wrong.
Are you still stuck?
If you can’t solve your problem using the troubleshooting guides: