This page has an error. You might just need to refresh it.
[Unhandled Promise Rejection: Definition for module "runtime_feature_usage_sdk/featureUsageCollector" was not found]
Tableau pulse takes time to load the metrics for large datasets and metrics containing a lot of filters.
Lösning
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.
Ytterligare resurser
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-artikelnummer
002330980
Löste denna artikel ditt problem?
Berätta för oss vad vi kan förbättra!
Fel notis.
Error
An error occurred during retrieving a vote
Tryck på Ctrl + F6 för att navigera till nästa toastmeddelande eller fokuserbara område.
Fel notis.Error An error occurred during retrieving a vote Tryck på Ctrl + F6 för att navigera till nästa toastmeddelande eller fokuserbara område.
Laddar
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.