Which adjustments are suggested to optimize Tableau for extracts?

Isolating the backgrounder on a second node is suggested as an adjustment to optimize Tableau for extracts because it allows for improved performance and resource management. The backgrounder process is responsible for executing scheduled tasks, such as refreshing extracts and managing subscriptions. By isolating these processes on a dedicated node, you can reduce competition for resources with other processes, such as VizQL, which are responsible for rendering visualizations.

This separation ensures that the background tasks do not interfere with the performance of interactive queries that are being executed by users. Consequently, this leads to a more efficient workflow, where extract refreshes can happen concurrently without affecting the responsiveness of dashboards and other visualizations being accessed by users. The optimization enhances the overall experience in a multi-user environment, especially as the volume of data and number of users increase.

Other adjustments, such as focusing on reducing VizQL processes or eliminating Cache Server processes, could lead to less optimal performance and may hinder user interaction. Running all processes on a single node would not effectively distribute the workload, leading to potential bottlenecks and affecting both background tasks and user queries adversely. Therefore, isolating the backgrounder enhances the ability to manage and execute extract jobs efficiently within Tableau.