Loading
Salesforce now sends email only from verified domains. Read More

How to improve Tableau Pulse performance

Publish Date: May 7, 2026
Description

Tableau pulse takes time to load the metrics for large datasets and metrics containing a lot of filters. 

Resolution
  • Performance is better while using an extract connection over a live connection.
  • It depends on the number of unique values in dimensions, the # of dimensions being used as adjustable metric filters. You need to take note of how many Metric Filters are part of the Metric Definition.
  • Do not create a single Metric Definition (MD) to serve all business areas.

The reason for this is that at runtime, Pulse is doing significantly more 'heavy lifting' behind the scenes than rendering a visualization. More and more intense queries are being made and calculations are happening behind the scenes to determine things like drivers, contributors, etc.

Additional Resources

For example, for the metric "Revenue", the metric filters that are interesting to Sales vs Marketing vs Prod Mgmt can be different. So instead of one MD that contains ALL of the metric filters, create a Revenue MD for Sales (with an MD Filter of Dept=Sales) with those specific metric filters and another Revenue MD for Marketing (with an MD Filter of Dept=Marketing) with those specific metric filters, etc.

However, performance is going to be a function not only of the # of those adjustable metric filters but also of the # of unique dimension values. For example, a "Region" dimension (North, East, South, West) would have less of an impact on performance than "State" (Alabama, Alaska ... Wyoming) which would have less of an impact on performance than "City" (New York, LA, Miami ... etc.)

Knowledge Article Number

002330980

 
Loading
Salesforce Help | Article