Query performance tuning in Tableau - Dashboard Guide

Dashboard Mode - Query performance tuning

Dashboard Goal

Understand how query performance tuning affects dashboard speed and responsiveness in Tableau.

Sample Data: Query Performance Metrics

Query ID	Execution Time (seconds)	Rows Returned	Cache Status	Optimization Applied
Q1	12.5	15000	No	None
Q2	4.2	15000	Yes	Indexing
Q3	7.8	8000	No	Filter Pushdown
Q4	3.5	8000	Yes	Filter Pushdown + Indexing
Q5	15.0	30000	No	None
Q6	5.0	30000	Yes	Indexing

Dashboard Components

• KPI Card: Average Execution Time
  Formula: AVG([Execution Time (seconds)])
  Shows the average query execution time across all queries.
• KPI Card: Average Execution Time (Cached Queries)
  Formula: AVG(IF [Cache Status] = 'Yes' THEN [Execution Time (seconds)] ELSE NULL END)
  Shows average execution time for cached queries only.
• Bar Chart: Execution Time by Query ID
  X-axis: Query ID
  Y-axis: Execution Time (seconds)
  Color: Optimization Applied
  Shows how different optimizations affect execution time per query.
• Table: Query Details
  Columns: Query ID, Execution Time (seconds), Rows Returned, Cache Status, Optimization Applied
  Shows detailed data for each query.

Dashboard Layout

+----------------------+-----------------------------+
| Average Execution Time| Average Execution Time (Cached)|
|       KPI Card        |          KPI Card            |
+----------------------+-----------------------------+
|                                                      |
|           Bar Chart: Execution Time by Query ID       |
|                                                      |
+------------------------------------------------------+
|                                                      |
|                   Table: Query Details                |
|                                                      |
+------------------------------------------------------+
    

Interactivity

Filter: Optimization Applied
Selecting one or more optimization types filters the bar chart and table to show only queries with those optimizations.
The KPI cards update to reflect average execution times for the filtered queries.

Filter: Cache Status
Choosing 'Yes' or 'No' filters all components to show cached or non-cached queries only.
This helps compare performance impact of caching.

Self Check

Add a filter for Optimization Applied = 'Indexing'.
Which components update and what changes do you see?

Answer:
The bar chart and table update to show only queries Q2, Q4, and Q6.
The KPI cards recalculate average execution times for these queries.
You will see that queries with indexing have lower execution times compared to those without.

Key Result

Dashboard shows how query optimizations and caching affect execution time in Tableau queries.

Practice

1. What is the primary purpose of using Tableau's Performance Recorder?

easy

A. To schedule data refreshes

B. To identify slow queries and dashboard actions for optimization

C. To export data to Excel

D. To create new visualizations automatically

Solution

1. Step 1: Understand Performance Recorder's role

   Performance Recorder tracks how long queries and dashboard actions take to run.

2. Step 2: Identify its main use

   This helps users find slow parts to improve dashboard speed.

3. Final Answer:

   To identify slow queries and dashboard actions for optimization -> Option B

4. Quick Check:

   Performance Recorder = Identify slow parts [OK]

Hint: Performance Recorder finds slow dashboard parts fast [OK]

Common Mistakes:

• Thinking it creates visualizations
• Confusing it with data export tools
• Assuming it schedules refreshes

2. Which of the following is the correct way to enable Performance Recorder in Tableau?

easy

A. Use the Data menu to activate Performance Recorder

B. Right-click on a worksheet and select 'Enable Performance Recorder'

C. Click on Dashboard > Performance Settings > Enable

D. Go to Help > Settings and Performance > Start Performance Recording

Solution

1. Step 1: Locate Performance Recorder in Tableau menus

   Performance Recorder is started from the Help menu under Settings and Performance.

2. Step 2: Confirm correct menu path

   The correct path is Help > Settings and Performance > Start Performance Recording.

3. Final Answer:

   Go to Help > Settings and Performance > Start Performance Recording -> Option D

4. Quick Check:

   Performance Recorder start = Help menu [OK]

Hint: Performance Recorder starts from Help menu [OK]

Common Mistakes:

• Looking under Data or Dashboard menus
• Right-clicking worksheet expecting option
• Assuming a separate settings panel

3. Consider a Tableau dashboard with many filters applied on live data. Which change is most likely to improve query performance?

medium

A. Replace live connection with an extract

B. Add more filters to narrow data further

C. Use complex calculated fields for filtering

D. Increase the number of worksheets in the dashboard

Solution

1. Step 1: Understand impact of live connections

   Live connections query the database every time, which can be slow with many filters.

2. Step 2: Use extracts to improve speed

   Extracts store data locally and speed up queries by reducing database load.

3. Final Answer:

   Replace live connection with an extract -> Option A

4. Quick Check:

   Extracts speed queries better than live connections [OK]

Hint: Use extracts to speed up slow live queries [OK]

Common Mistakes:

• Adding more filters increases query time
• Complex calculations slow performance
• More worksheets increase load, not reduce

4. You notice your Tableau dashboard is slow. You see this calculation: IF [Sales] > 1000 THEN [Profit] ELSE 0 END. What is a likely fix to improve performance?

medium

A. Replace the calculation with a simple filter on Sales > 1000

B. Add more nested IF statements

C. Use a string function instead of IF

D. Remove all filters from the dashboard

Solution

1. Step 1: Analyze calculation impact

   Calculations inside dashboards can slow queries, especially row-by-row IF statements.

2. Step 2: Simplify by filtering data first

   Filtering data before calculations reduces rows processed and speeds performance.

3. Final Answer:

   Replace the calculation with a simple filter on Sales > 1000 -> Option A

4. Quick Check:

   Filtering before calculation improves speed [OK]

Hint: Filter data before calculations to boost speed [OK]

Common Mistakes:

• Adding more IFs increases complexity
• Using string functions unrelated to numeric filters
• Removing filters can increase data load

5. A Tableau dashboard uses multiple data sources with complex joins and many filters. Performance is poor. Which combined approach best improves query speed?

hard

A. Increase dashboard size and add more worksheets

B. Keep live connections but add more calculated fields

C. Use extracts for data sources, reduce filters, and simplify joins

D. Remove extracts and rely only on live data

Solution

1. Step 1: Identify performance bottlenecks

   Complex joins and many filters slow queries, especially on live data sources.

2. Step 2: Apply combined fixes

   Using extracts reduces database load, fewer filters reduce query complexity, and simpler joins speed data retrieval.

3. Step 3: Avoid opposite actions

   Adding calculated fields or more worksheets increases load; removing extracts loses speed benefits.

4. Final Answer:

   Use extracts for data sources, reduce filters, and simplify joins -> Option C

5. Quick Check:

   Extracts + fewer filters + simple joins = faster queries [OK]

Hint: Combine extracts, fewer filters, simpler joins for best speed [OK]

Common Mistakes:

• Adding more calculated fields slows performance
• Increasing dashboard size adds load
• Removing extracts loses caching benefits