Tableau Prep Flow Authoring

The Tableau Prep Flow Authoring process provides the interactive Prep Flow experience in the browser, which lets users create and interact with flows on Tableau Server to clean and prepare data. For more information, see Create and Interact with Flows on the Web. It was added in version 2020.4.

Process

Tableau Prep Flow Authoring

Status Status of the Tableau Prep Flow Authoring process is visible on the Status Page. For more information, see View Server Process Status
Logging Logs generated by the Tableau Prep Flow Authoring process are located in /var/opt/tableau/tableau_server/data/tabsvc/logs/floweditor. For more information, see Tableau Server Logs and Log File Locations

Tableau Prep Flow Authoring is enabled by default. It uses these components:

  • Tableau Prep Minerva Service: Used by Tableau Prep Flow Authoring for querying datasources. By default, it is automatically enabled on a node where Tableau Prep Flow Authoring is enabled.
  • Data Engine: The Data Engine creates data extracts and processes queries. By default, it is automatically enabled on a node where Tableau Prep Flow Authoring is enabled.

Performance and Scale Recommendations

Tableau Prep Flow Authoring can be CPU and RAM intensive. It is recommended to monitor server and adjust your deployment as necessary by isolating flow authoring to a separate node or adding server resources.

Isolate flow authoring to a separate node

Running Tableau Prep Flow Authoring on a separate node will isolate flow authoring workflows from other Tableau workloads. If you have a busy server with many extract refreshes, and a lot of viz editing and viewing and you don't want to cause disruption to this workload, then it is recommended to isolate Prep Flow Authoring to its own server node. This means that all flow editing will be directed to a dedicated node. You can also choose to isolate all background workloads such as backgrounders and Tableau Prep Conductor from all your interactive workloads such as Prep Flow Authoring and VizQL Server.

Add resources

As you need more resources, you can add more nodes to your server environment. When planning your nodes, several factors can influence your decision on how much additional hardware you need to allocate.

 The main things to consider when planning your nodes are:

  • The number of concurrent users or concurrent sessions you expect during peak hours. The number of concurrent sessions per user can be set using the TSM option maestro.sessionmanagement.maxConcurrentSessionPerUser. For more information, see tsm configuration set Options.
  • The number of data input nodes your flows have on average and the amount of data they have. The maximum row sampling limit can be set using the TSM option maestro.app_settings.sampling_max_row_limit. For more information, see tsm configuration set Options.
  • The complexity of the flows being authored and the number of nodes. Node types like joins, unions, aggregates, and pivots will, in general, require more resources.

Topology and Configuration

To make Tableau Prep Flow Authoring highly available, configure two instances of Tableau Prep Flow Authoring on nodes when enabling it.

Here is an example of a two node configuration:

Example of a two node configuration

Here is an example of status page for a two node configuration:

Example of status of a two node configuration

Here is an example of a four node configuration:

Example of a two node configuration

Here is an example of status page for a four node configuration:

Example of status of a two node configuration

Thanks for your feedback!