---
schema_version: "1"
id: a11aae2d1c8eb420c7926400e455c00bd38e04646ec9b677ead17ea35ae6b9c4
title: Optimise Workbook Performance
collection: tableau
version: next
locale: en-gb
portal_url: https://docs.salesforce.com/tableau/next/en-gb/pro/desktop/performance_tips.md
canonical_url: https://help.tableau.com/v0.0/pro/desktop/en-gb/performance_tips.htm
source_site: help.tableau.com
content_type: documentation
content_hash: c1112210ea90d920a7779df35a362a8d5e0ace52d82ab842d82ae906957d5fa9
description: Overview of tips for optimizing workbook performance in Tableau.
---
[Skip to main content](#main-content)

# Optimise Workbook Performance

When we mention _performance_, we mean the speed with which you can work in Tableau. It might mean the speed of data analysis, such as working in Tableau Desktop on a large corporate database that you are accessing remotely. Or, it could refer to the speed of loading views or dashboards that you access on your desktop from Tableau Server.

If you are working with small data volumes, many of the recommendations in this section are optional for you. Your workbook performance is probably as speedy as you expect. But if you work with hundreds of millions of records, designing an efficient workbook is critically important to the speed at which you can work. We recommend that you review the topics and tips in this section before you start building your first view.

Making performance improvements almost always means making trade-offs. For example: Do you sacrifice speed to make sure you have the most current data? Is it important to include _all_ the data for analysis, or will a speedier subset do? The bigger and more complicated the data, the longer it takes to interpret and render. But there are things you can do to accelerate the process. Think of fine-tuning your workbook performance as working on a puzzle with multiple pieces. Pick and choose from the topics in this section to find the pieces that solve your particular puzzle.

The topics in this section on performance discuss the big picture and then drill down to specific functionality. It starts with databases, data and extracts, and then focuses on things that affect your data source, your workbooks, your calculations and visualisations. The next set of topics discuss how to record and analyse workbook performance. Finally we look at how to reduce upload times to a Tableau server.

**Learn more**: For more in-depth and related information beyond this topic, see:  
[Designing Efficient Workbooks](https://www.tableau.com/en-gb/learn/whitepapers/designing-efficient-workbooks) whitepaper on tableau.com  
[Designing Efficient Workbooks](https://youtu.be/Si_ieb51DSs) (1 hour) and [Best Practices for Dashboard Performance](https://youtu.be/D2dzCp9CBy0) (50 minutes) free, video presentations  
[The Tableau Performance Optimisation Flowchart](https://interworks.com/blog/rrouse/2018/05/16/the-tableau-performance-optimization-flowchart/), [The Tableau Performance Checklist](https://interworks.com/blog/bfair/2015/02/23/tableau-performance-checklist/) and the [Tableau Performance Checklist blog series](https://interworks.com/blog/series/the-tableau-performance-checklist) on the [InterWorks blog](https://interworks.com/blog/).

## General tips

This general list of considerations is a start in learning how to approach optimising workbooks. It comes from the TL;DR page in the [Designing Efficient Workbooks](https://www.tableau.com/en-gb/learn/whitepapers/designing-efficient-workbooks) whitepaper.

- The cleaner your data is and the better it matches the structure of your questions, the faster your workbooks will run and the happier your life will be. Only connect to the data that you need for analysis.
- Extracts are a quick and easy way to make most workbooks run faster. If you don’t need real-time data and aren’t working over billions of rows of data, you should try them.
- The majority of slow dashboards are caused by poor design – in particular, too many charts on a single dashboard, or trying to show too much data at once. Keep it simple. Allow your users to incrementally drill down to details, rather than trying to show everything then filter (guided analysis).
- Don’t work with data you don’t need – both in terms of the fields you reference as well as the granularity of the records you return. Use filters, hide unused fields and aggregate.
- While reducing the data, make sure you use filters efficiently.
- Strings and dates are slow, numbers and Booleans are fast.
- There is no silver bullet for inefficient workbooks. Start by looking at the performance recorder to understand where the time is going. Long-running queries? Lots of queries? Slow calculations? Complex rendering? Use this insight to focus your efforts in the right direction.
- Upgrading to the newest version may boost performance without needing anything else.
- If it is slow in the data source, it will be slow in Tableau Desktop. If it is slow in Tableau Desktop, it will (almost always) be slow in Tableau Server.
- Performance tuning is highly individualised to the context of your environment, data, analysis and workbook. What works in one situation may not work in another test and iterate to see what works in your specific case.

## Other articles in this section