View Acceleration loads views faster by precomputing and fetching the workbook's data in a background process. There are two potential bottlenecks when loading a view:

  1. Querying (fetching data from the data source).
  2. Rendering (creating the visuals, such as drawing shapes or rendering a map).

The time it takes to load a workbook depends on the combined time it takes to do these two steps. However, not all views can be accelerated. View Acceleration improves the performance of the query step, so a workbook performance won’t improve significantly if its query step is already fast and there isn’t a performance bottleneck on load.

In addition, View Acceleration relies on precomputation. The following factors impact the effectiveness of View Acceleration:

  • A view uses transient functions, such as now() or today().
  • A view relies on user-based functions to provide different results for different users. Even though Tableau Server could precompute results for all users, doing so significantly increases CPU, memory, and storage usage.
  • A view has an extract refresh schedule that exceeds the daily limit. Accelerated views are regenerated when the extract is refreshed. To limit resource consumption, we limit the maximum number of jobs that can be run (6 per day).
  • A view uses a published data source that exceeds the maximum number of daily extract refreshes (6 per day). This limitation applies to Tableau Online only.
  • A view’s owner is inactive. Acceleration jobs run on behalf of the view owner. If the owner is inactive, then the job fails.
  • A view can’t be loaded because the embedded credentials expired or the data source was deleted.

When users create custom views on top of an existing view and accelerate the custom view, both the original view and the custom view are accelerated. However, if a custom view hasn’t been accessed in the last 14 days, then the custom view can’t be accelerated. Finally, in addition to the original view, up to 10 custom views can be accelerated for each original view.

Note: View Acceleration isn’t available in Tableau Desktop.

Accelerate your view

  1. Sign in to a site on Tableau Online or Tableau Server.
  2. From the Home or Explore page, navigate to the view you want to accelerate.
  3. Click the Accelerate icon, and toggle the switch to Accelerate.

View Acceleration window

You can also accelerate views from the workbook page:

Workbook page with Actions selected and and Acceleration menu open

Understand why View Acceleration is unavailable

There are a few reasons that acceleration isn’t available for a view. Acceleration precomputes long-running queries, so accelerated workbooks load faster. But if the view is already loading as fast as it can, then acceleration isn’t available because acceleration won’t significantly improve the performance of the view.

Similarly, if you use a data freshness policy that is less than 4 hours, then acceleration isn’t available because the cost is high for accelerating the views that are refreshed so frequently, and Tableau doesn’t want to overload your site performance. For more information, see Set a Data Freshness Policy.

If your administrator has suspended acceleration for your view, then contact your Tableau administrator to activate acceleration for your view. Similarly, if the site has reached the limit for the number of views that can be accelerated for your site, then contact your Tableau administrator.

To precompute the data, Tableau needs to connect to the data source in the background without requiring user interaction. Therefore, View Acceleration is only supported for workbooks with embedded connection credentials. And finally, views that use encrypted extracts can’t be accelerated because Tableau can’t access or accelerate an encrypted data source extract.

Allow View Acceleration on your site

Workbooks are not enabled for acceleration by default.

  1. Sign into your site on Tableau Server.
  2. From the left pane, choose Settings.
  3. From the General tab, scroll to the View Acceleration section.
  4. Check the box to allow creators and explorers to accelerate views in their workbooks.
  5. Enter the maximum number of views that can be accelerated for your site, or choose No limit.

View Accelerations settings

View and manage accelerated workbooks

  1. Sign into your Tableau site.
  2. From the left pane, choose Tasks.
  3. Click the Accelerated Views tab.
  4. Choose the Actions menu (...) to Resume or Suspend Acceleration for the selected view or views.

Accelerated Views tab from Tasks page

Understand user Context for Precomputation

Precomputation for accelerated workbooks is performed with the user context of only one user. This user is either:

  • The owner of the workbook (if there are no user filters in the workbook or data source, or if there are user filters on the data source but the data source is a published data source).
    -or-
  • The user that was selected for thumbnail generation the last time the workbook was published (if there are user filters on the workbook and the data source is not a published data source).

Understand the cost of View Acceleration

Enabling this feature increases the computation load and number of jobs on Tableau Server backgrounder processes because View Acceleration fetches the required data from data sources in a background process. A background job to precompute the data of an enabled workbook is run if any of the following happen:

  • The workbook and published data source are republished (this includes the web-authoring save).
  • An extract used by the workbook is refreshed.

Administrators should consider those costs before enabling View Acceleration for many workbooks, or scheduling acceleration jobs too frequently.

  • Workbooks that are being heavily edited and republished might not be suitable because each republish triggers a precomputation. We recommend acceleration for workbooks that are published for consumption.
  • If a workbook uses multiple extracts, then their refresh triggers precomputation of the data. Thus, frequent extract refreshes for enabled workbooks could cause a spike in backgrounder job load, especially given that by design View Acceleration jobs are run after the successful extract refresh.
  • The precomputed data for workbooks is stored on disk. Thus, acceleration can increase the disk storage of the server.
Thanks for your feedback!