Tableau Cloud Help

Storage

A site comes with site and individual content storage capacities.

• Site storage: A site comes with 1 TB of storage capacity. Workbooks, published data sources, and flows count toward this storage capacity.

  Note: Sites with Enterprise edition, Tableau+ edition, or the Advanced Management add-on get 5 TB of site storage.

• Individual workbook, published data source, and flow size: An individual workbook, data source (live or extract), or flow published to your site should not exceed 25 GB. Content should not exceed that size for optimal performance and to avoid other constraints, such as query usage and runtime limits.

  Note: If your extract data source exceeds 10 GB in size, we recommend that you consider using live connection to the database, aggregate the data in the extract to reduce its size, or use incremental extracts. Frequently republishing or refreshing large full extracts can be time intensive and usually indicates that more efficient data freshness strategies should be considered.

Extracts - daily, runtime, and memory usage

A site comes with designated capacity for extract refresh daily jobs, runtime, and memory usage.

• Daily jobs: Daily jobs capacity is the number of shared hours each site can spend per Creator license a day to perform all jobs on the site. A server process, called backgrounder, initiates and performs these jobs. A site with more Creator licenses gets more daily jobs (backgrounder) capacity to meet the needs of a larger site population.

  For example:

  If your site has...	multiplied by the default time	Daily jobs capacity
  10 Creator licenses	8 hours	Up to 80 hours/day
  50 Creator licenses	8 hours	Up to 400 hours/day

  Daily jobs capacity resets each day at 24:00:00 UTC (coordinated universal time).

  About extract refreshes

  Refresh jobs that count toward daily jobs capacity include full and incremental refreshes and extract creation, which can be initiated by scheduled refreshes, manual refreshes, and certain command line or API calls.

  Notes:

  • As long as your site has time remaining in its daily refresh capacity, a refresh job will start.
  • Site admins receive email notifications when a site reaches 70%, 90%, and 100% of its daily refresh capacity.
  • If a site exhausts its daily refresh capacity, any future extract refreshes are canceled and email notifications are sent to content owners alerting them of the refresh cancellation.

• Job runtime: Each extract refresh job type has a maximum runtime of two hours (120 minutes or 7,200 seconds). If a refresh job reaches its maximum runtime, you see a timeout error. For more information about the error and ways you can modify extracts to keep refresh jobs within the runtime capacity, see Time limit for extract refreshes.

• Refresh memory usage: A site has capacity to use no more than 20 GB of memory to refresh an extract. The amount of memory needed to refresh extracts can vary depending on the size of the extract and other factors.

Tips for optimizing extract refresh capacity

If you're managing an extract-heavy environment, Tableau recommends following some best practices to make the most efficient use of your extract refresh capacity.

• Stop refreshing unused extracts. One of the best ways to reclaim capacity for your site is to stop automatic refreshes, either through schedules on Tableau Cloud or through scripts of extracts that aren’t being used. For more information about deleting a refresh schedule, see Manage Tasks.

• Reduce the frequency of refreshes. Another method of reclaiming capacity for your site is to reduce the frequency of extract refreshes. For example, instead of refreshing an extract hourly, consider refreshing an extract daily or only during business hours when fresh data is most useful. For more information about changing a refresh schedule, see Manage Tasks.

• Use incremental refreshes instead of full refreshes. To decrease the amount of time an extract takes to refresh, consider performing an incremental refresh of the extract instead of a full refresh. For more information, see Schedule Refreshes on Tableau Cloud.

  Note: Changing from a full to an incremental refresh can be done from Tableau Cloud only if the extract was configured for incremental refresh in Tableau Desktop before the extract was published. For more information about incremental refreshes, see Configure an incremental extract refresh(Link opens in a new window) in the Tableau User Help.

• Use live connections instead of extract connections. For views, dashboards, and workbooks whose data needs to be updated frequently, consider setting up the data source to use a live connection instead of an extract connection.

• Optimize the data in the extract. Improving the performance of an extract can also help reduce the amount of time an extract takes to refresh. There are a number of changes you can make to the extract's data to help its overall performance, such as removing unused fields, using filters to remove unused rows, and changing date ranges.

Subscriptions - runtime and email size

A site comes with designated capacity for subscription runtime and email size.

• Job runtime: Each subscription job has a maximum runtime of 30 minutes (1,800 seconds).

• Email size: A subscription email can be a maximum size of 2 MB.

Flows - user requests, runtime and memory usage

A site comes with designated capacity for flow user requests, runtime, and memory usage.

• User request rate: Each user can have a maximum of 4 active flow web editing sessions at one time. If more sessions are opened, the oldest session will be closed.

• Job runtime: For sites with Data Management, you can run flows for up to 24 hours per day per Resource Block. If you exceed the time limit, no new jobs can be started until the next day. Additional capacity for concurrent flow jobs can be purchased. For more information, see Resource Blocks.

• Flow memory usage: A site has capacity to use no more than 19.5 GB of memory for a flow job.

Visualizations

A site comes with designated capacity to load and query individual visualizations, also known as views. You can find more information about each capacity type below.

• Load time: A site has capacity to spend up to 5 minutes to load a view.

• Idle timeout: If the user hasn’t interacted with or edited a view for 120 consecutive minutes, the user must reload (for example, refresh the page or click the Reconnect button if a banner displays) the view or saved draft to interact with it again.

• User request rate: Each user on a site has the capacity to make up to 600 requests per hour to load and refresh views. When this capacity has been reached, the user can't interact with, edit, and save the view. After an hour, the view can be refreshed and new views can be loaded.

  Note: If the cumulative number of user requests exceeds the site-level request rate, users can’t interact with, edit, and save views.

• Query memory usage size: A site has capacity to use no more than 20 GB of memory to query a view that uses an extract data source. The amount of memory needed to query a view can vary depending on the complexity of the data manipulations that Tableau needs to perform to generate the marks in the view.

Views that exceed these capacity types might be canceled to ensure enough system resources are available so that other views on the site can load.

Tips for optimizing visualization capacity

Views that exceed visualization capacity can indicate the queries that Tableau must run in order to generate the view might be too complex. In such cases, you can use the following tips to help optimize queries thereby minimizing the time it takes to load views on Tableau Cloud. Most tips require that you edit the data source or workbook and republish to Tableau Cloud for changes to take effect.

For more tips, see the Workbook Performance(Link opens in a new window) topic in the Tableau Help.

• Use data source filters: When you add a filter on a data source, you reduce the amount of data that needs to be generated in the view. Reducing the amount of data can help minimize load times of views. For more information, see Filter Data from Data Sources(Link opens in a new window) in the Tableau Help.

• Use context filters: Similar to data source filters, context filters reduce the data in the data source but at the sheet level. Context filters work independently of other filters and can significantly reduce the amount of data that needs to be generated in the view. Reducing the amount of data can help minimize load times of views. For more information, see Improve View Performance with Context Filters in the Tableau Help.

• Decrease date ranges: As a rule, dates require more computing power than other types of data like numbers and Booleans. If the view contains date filters, you can reduce the date ranges or the number of dates that need to be generated to help minimize the load times of views.

• Reduce marks: Because Tableau must calculate the marks in order to generate the view, the number of marks can impact how quickly the view can load. There are several ways you can reduce marks, including using some of the filters listed above or using sets to filter, custom SQL to aggregate data, and so on. For more information, see Reduce the number of marks in the view(Link opens in a new window).

View Acceleration

A site has the following View Acceleration capacity:

• Accelerated views: The default number of accelerated views per site is 30. For each additional Creator license, 20 more views can be accelerated. The maximum number of accelerated views is 750.

• Accelerated views refreshes: Accelerated views refreshes are regenerated in alignment with the following four data update events:

  • Data freshness policy: The acceleration timestamp is out of sync with the data freshness policy.
  • Extract refreshes: An extract refresh completes, signaling fresher data.
  • Accelerated view update: An accelerated view is updated by the owner.
  • View opted-in: A view is originally opted in for acceleration.

  Each unique event triggers a pre-computation job to be queued. Backgrounder jobs then pick up and complete the pre-computation, and then store query results as a materialized view. Views that belong to the same workbook are refreshed in one job. To limit resource consumption, the maximum number of pre-computation jobs that can be run is limited to 12 jobs per day. For more information, see Set a Data Freshness Policy.
  

• Accelerated views memory usage size: A site has capacity to use no more than 20 GB of memory for pre-computing and fetching the workbook's data in a backgrounder job. The amount of memory needed varies depending on the complexity of the queries that are associated with the view that is being accelerated.

• Job runtime: View acceleration has a maximum runtime of 30 minutes (1,800 seconds).

Additional APIs and command line calls

A site comes with designated capacity for API and command line calls. The site is equipped with capacity for the following:

• Query Job(Link opens in a new window) and Cancel Job(Link opens in a new window) (Tableau REST API) and Tableau Client (Python) library(Link opens in a new window): A site allows 20000 calls per 24-hour period.

• Get Users on Site(Link opens in a new window) (Tableau REST API): A site allows 5000 calls per minute.

• Remove User from Site(Link opens in a new window) (Tableau REST API): A site allows 1600 calls per minute.

Note: If the number of calls exceed the API or command line calls described above, you see one of the following errors: Unknown 429 or ApiCallError: 429000: Too Many Requests – Too many requests for <job type> ‘api.rest.refresh_extracts’. Please retry after 146 second(s).