Skip to content
Docs
Open Mammoth
Learn › Help › Slow pipelines: open the docs menu

Speed up a slow Mammoth dashboard or AI dashboard build

A dashboard doesn't query its source Views each time someone opens it. New rows come into the dashboard's draft when it syncs (Sync new data: "Pull new rows from connected datasets into your draft"), and viewers see them after you publish. So a slow dashboard usually waits on one of these:

  • the source View's pipeline run, before the dashboard can sync
  • the sync itself, when a source View holds millions of unaggregated rows
  • a publish: viewers see the last published version until you publish or turn on Publish new data automatically

Check the dashboard's sync status

  1. Open the dashboard's Updates window, from the Dashboards library or the editor's state line.
  2. Under Sync new data, check whether each source shows New data or Up to date, and when it last updated.
  3. If you see "New source data is waiting to sync.", click Sync on each source marked New data. There is no single button for all sources.
  4. Publish the dashboard.

See Manage your dashboards.

Aggregate and filter the View behind the dashboard

  • Aggregate. For KPIs, totals and summary charts, the View should hold aggregated data, not row-level records. Add a Group & Pivot task at the end of the pipeline that summarises to the grain the dashboard needs. For monthly revenue by region, that's one row per month and region, not one per transaction.
  • Pre-filter. Add a Conditional Filter task to limit the View to what the dashboard shows. If it shows the last 12 months of sales, filter the View to the last 12 months, not all history.
  • Speed up the source pipeline. If the source View's pipeline is the slow part, see Speed up Mammoth pipelines.

Speed up AI dashboard generation

Building a dashboard with AI takes a short while, because the AI reads your View's columns and data before it builds charts. See Create a dashboard. If the build seems stuck:

  1. Refresh the page and try again.
  2. If it keeps happening, simplify the prompt and reduce the number of columns in the source View. Narrow Views with a few focused columns generate faster than wide ones.
Was this page helpful?

Something wrong? support@mammoth.io