Performance Tuning

This section describes how to use the performance data that you collect to identify ways to improve the performance of Tableau Server. Because no two server environments are identical, we can't provide hard and fast rules for tuning server performance. However, you can draw conclusions about performance from patterns in the data that you collected.

For example, are there recurring spikes? Do any of the patterns that you notice in the administrative views correspond to similar patterns in Windows Performance Monitor? Observing patterns like this can guide you in testing and incremental tuning.

Most performance tuning for Tableau Server boils down to these general approaches:

  • Optimise for User Traffic: This tunes the server to respond to user requests and to display views quickly.

  • Optimise for Extracts: This tunes the server to refresh extracts for published data sources. You might want to optimise for extract refreshes if your organisation has a lot of data and the data needs to be as up to date as possible.

  • Optimise for Query Heavy Environments: This is a specialised server configuration to optimise for query performance of workbooks that use extracts as their data source.

Rendering views and refreshing extracts generate the most load on the server, so you should optimise for the task that your organisation is most interested in.

As a best practice, optimise your workbooks for performance. For more information and resources on how to optimise your workbooks, see Optimise Workbook Performance.

Topics in this section:

Thanks for your feedback!