Diagnosing performance bottlenecks and tuning caches
Find the root cause of slow Tableau Server content (workbook, data source, user traffic, background jobs or resources) with the sample performance workbook, admin views, RMT and performance recordings, then act on it with workbook fixes, schedule and process changes, rendering thresholds, cache and session settings.
3.3 Identify and resolve performance bottlenecks: 3.3.1 Troubleshoot complex performance issues related to workbooks, data sources, and other types of content; 3.3.2 Perform resource analysis, latency analysis, and workload analysis to determine root cause of performance issues; 3.3.3 Create an action to resolve issues identified in performance recordings; 3.3.4 Optimize caching for Tableau Server.
~7 min read · 21 practice questions
What the exam expects
- Troubleshoot slow workbooks, data sources and other content, and separate a content problem from a server-wide one.
- Perform resource, latency and workload analysis with the sample performance workbook, admin views and the Resource Monitoring Tool.
- Turn performance recording events into a concrete action.
- Optimize caching, rendering and session memory on Tableau Server.
Key terms: sample performance workbook (repository-based dashboards for requests, sessions, background jobs, CPU and memory); Background Task Delay (admin view of time between a task's scheduled and actual start); performance recording (a workbook of timed events for one recorded session); query cache (stored query results, sized automatically unless set manually); Cache Server (shared external query cache process); complexity threshold (the point at which a view renders on the server instead of the browser).
Key facts
- Detail
- Peak above 1,000 VizQL sessions per hour
- Detail
- Do not change directly; contact Support
- Detail
- 95th percentile of 50 successful renders
- Detail
- Long from 2x, Very Long from 4x baseline
- Detail
- Parallel, on all available Backgrounders
- Detail
- Pages disagree: half the cores, or half to all cores on a separate node
- Detail
- At most six, at most two per node
- Detail
- Applying it restarts Tableau Server
- Detail
- 30 minutes by default
- Detail
- 100 computers, 60 mobile
- Detail
- Filter to one user request
Sources for this section (8)
- Performance guidelineshelp.tableau.com (opens in a new tab)
- Slow view loadshelp.tableau.com (opens in a new tab)
- Extractshelp.tableau.com (opens in a new tab)
- Backgrounder Processhelp.tableau.com (opens in a new tab)
- Cache Serverhelp.tableau.com (opens in a new tab)
- Data Cachehelp.tableau.com (opens in a new tab)
- Client-side renderinghelp.tableau.com (opens in a new tab)
- Performance recordinghelp.tableau.com (opens in a new tab)
- When does Tableau Server render a view on the server even though client-side rendering is on?
- Why do brief, recurring 100% spikes in Backgrounder CPU matter?
- Which key disables client-side rendering for the whole server?
- Which URL parameter re-enables client-side rendering for one session when it is disabled on the server?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Tableau Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 18 lessons of the Tableau Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (21 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both