Video | Tableau | Data visualisation | Productivity

How to start a performance recording in Tableau Desktop: Quick Tip

Once you hit Start, nothing happens on screen, you just have to trust it's kicked off.

Part ofTableau quick tips
Watch on YouTube
  • The performance recording option is hidden under Help > Settings and Performance > Start Performance Recording, and there's no on-screen confirmation that it's running
  • You confirm it's recording by going back to Help and seeing the option now reads 'Stop Performance Recording'
  • Cycle through tabs and interact with filters during recording so you capture both live data source loads and faster cached loads
  • The filter at the top of the recording workbook hides quick activities; slide it left to see everything, then sort by query performance to find the slowest tasks
  • A common workflow is to record set steps before and after optimising a workbook, then compare activity times to measure improvement

Tim shows where Tableau Desktop hides the performance recording feature and how to read the workbook it produces, so you can diagnose which interactions in a slow workbook are actually costing time.

Opening a Tableau workbook involves reading the XML, querying the data source, and rendering the visualisation — any of these can be slow, but you can't tell which just by watching. A performance recording captures timings for each step so you get quantitative numbers instead of a guess.

The Breakdown
  1. What actually happens when you open a workbook 0:32

    Opening a workbook loads the XML file, queries the data source, then the Viz QL engine renders the visualisation on screen. Any of these stages can be the source of slow performance, which is why you need a way to measure each one separately.

  2. Why bother recording performance 0:55

    If a workbook feels slow, a performance recording lets you diagnose whether it's a complex query, a heavy calculation, or something else, rather than just guessing that an interaction 'feels fast or slow'.

  3. Start it from the Help menu 1:42

    Go to Help > Settings and Performance > Start Performance Recording. Nothing visibly happens on screen when you click it — there's no icon or confirmation, so you have to trust it has started.

  4. Confirm it's actually running 2:20

    The only way to check the recording is live is to reopen the Help menu and see the option now reads 'Stop Performance Recording'. This must be done after starting, since it's the sole confirmation available.

  5. Interact deliberately while recording 2:33

    Cycle through tabs you haven't yet opened to capture genuine data source loads, then revisit tabs and toggle filters to also capture cached loads (where Tableau reuses data it already holds in memory). Doing both gives you a fuller picture of live versus cached performance.

  6. Stop and open the recording workbook 4:01

    Stopping the recording via the same Help menu path opens a workbook automatically — this can take a moment on a slow machine or with a large recorded session.

  7. Read the recording: filter and sort 4:16

    The top filter often hides very fast (near-zero-second) activities by default; slide it fully left to see everything. Sort by query performance to rank activities from slowest to fastest and spot the real bottlenecks, and click into an activity to see the actual query sent to a live database.

  8. Use the detailed timeline and compare before/after 6:40

    The detailed view is a Gantt-style chronological chart where higher-level activities spawn the lower ones beneath them, showing what triggered what. A common approach is to record a set sequence of steps before optimising, then repeat exactly the same steps afterwards and compare activity times to measure the improvement.

Worth Knowing
  • There's zero visual feedback when you click Start — you only confirm it worked by reopening the Help menu and checking the wording has changed to Stop.
  • The activity filter is sometimes pre-set away from zero, silently hiding fast tasks; you need to manually slide it to the far left to see the complete list.
  • Extremely fast activities can register as 0.00 seconds, which is likely why the workbook filters them out by default.
  • This isn't a live database example, so the query detail view is less rich here than it would be against something like SQL Server, Oracle or Snowflake.
Use It When

Reach for this when a workbook feels sluggish and you need actual numbers — rather than a hunch — on which interaction, query or render step is the bottleneck, especially when comparing a workbook before and after you've tried to optimise it.

How this Rollup was made provenance & method

A Rollup is drafted by AI from the video's transcript, then reviewed and edited by Tim. Everything used to produce this one is listed below — the model, the exact prompt, and the source video — so the process is transparent and reproducible.

Transcription
On-device — NVIDIA Parakeet v3 for recent videos, OpenAI Whisper large-v3 for earlier ones. The transcript never leaves the machine or gets published.
Drafting
Claude Sonnet 5 in the cloud, from that transcript.
Prompt
The exact Rollup prompt (v2) — the full system prompt, unedited.
Source video
Watch on YouTube
Drafted
5 July 2026 at 09:38
Reviewed & edited
5 July 2026 at 09:41 · by Tim Ngwena

Model + prompt + video is everything you'd need to recreate a Rollup like this yourself. The one thing we don't share is the transcript.

Rights. The video and its transcript are the property of TN Media Ltd. Unauthorised use or download is prohibited. © TN Media Ltd.