The license is for a single Tableau Server deployment, which can be role-based or core-based.Īs a Creator, Data Management is not required to create and edit flows directly on your server.Ĭonfigure where the different types of workloads are processed through node rules. The Data Management license includes Tableau Prep Conductor, which enables you to schedule and track flows. Tableau Prep Conductor must be running on the node. OFFERINGĬonfigure a node to run only flows, or configure a node to run all jobs except flows. Node types like joins, unions, aggregates, and pivots will, in general, require more resources.Īdditional licenses for Data Management and Advanced Management are required for configuring nodes. The complexity of the flows being authored and the number of nodes. ![]() For more information, see tsm configuration set Options. The maximum row sampling limit can be set using the TSM option maestro.app_settings.sampling_max_row_limit. The number of data input nodes your flows have on average and the amount of data they have.The number of concurrent sessions per user can be set using the TSM option. The number of concurrent users or concurrent sessions you expect during peak hours.The main things to consider when planning your nodes are: When planning your nodes, several factors can influence your decision on how much additional hardware you need to allocate. Add resourcesĪs you need more resources, you can add more nodes to your server environment. While you can run flows on any licensed Server core, the additional resource cores purchases should only run Tableau Prep Conductor, and not extract refreshes or VizQL processes. For more information, see Tableau Server Backgrounder Process and Workload Management through Node Roles.įor core and user-based deployments, it’s strongly recommended that at least one node be dedicated to flows for best performance. Using the Backgrounder process, you can isolate background workloads such as Tableau Prep Conductor from all your interactive workloads such as Prep Flow Authoring and VizQL Server. If you are running Tableau Server on a multi-node cluster, you can dedicate one or more nodes for running Backgrounder. If those services are already at capacity, they might also need additional resources because of the additional Prep Web Authoring load. Note: Prep Web Authoring uses shared services such as the Application Server (VizPortal), the PostgreSQL repository, the Cache Server, and Hyper. ![]() For more information see Configure Nodes. This means that all flow editing is directed to a dedicated node. 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. Running Tableau Prep Flow Authoring on a separate node will isolate flow authoring workflows from other Tableau workloads. Isolate flow authoring to a separate node It is recommended to monitor server and adjust your deployment as necessary by isolating flow authoring to a separate node or adding server resources. Tableau Prep Flow Authoring can be CPU and RAM intensive. By default, it is automatically enabled on a node where Tableau Prep Flow Authoring is enabled.
0 Comments
Leave a Reply. |