Video | Tableau | Data visualisation | Productivity

How does Zone Visibility perform? | New in Tableau 2022.3

I use performance recording to crack open what Tableau really does behind hidden zones when you use zone visibility.

Part ofWhat's new in Tableau 2022.3
Watch on YouTube
  • Start performance recording before opening any workbook, via Help > Settings and Performance > Start Performance Recording, so the capture runs in the background from the very beginning
  • Leave deliberate gaps between actions when recording so each activity shows clearly on the resulting timeline
  • The performance recording output gives both an overview dashboard and a detailed event timeline you can rebuild by dropping fields like start index, event and worksheet onto the view
  • Tableau appears to run all queries and compute layouts for hidden zones up front, only rendering the visible zone when you switch to it, so heavy queries behind a hidden zone still load at the start
  • Click the green query items in the recording to see the actual SQL sent to the database for debugging

Tim investigates what actually happens behind the scenes when you hide a zone with zone visibility in Tableau, using performance recording to see whether hidden zones still cost you query and rendering time.

A viewer asked what happens to performance when a section is hidden using zone visibility. Tim uses a workbook with zone visibility switching between furniture, office and technology sections, wrapped in a performance recording, to find out.

The Breakdown
  1. Start performance recording before opening the workbook 0:23

    Open Tableau without loading a workbook first, then go to Help > Settings and Performance > Start Performance Recording. Starting it before you open anything means the capture runs in the background from the very first load, so you don't miss early activity.

  2. Leave gaps between actions as you record 1:00

    With recording running, open the workbook and then pause a few seconds between each interaction (switching zones, applying a filter) before doing the next one. Spacing actions out makes each one show up as a distinct, identifiable block on the resulting timeline rather than blurring together.

  3. Stop recording and open the results workbook 2:21

    Go back to Help > Settings and Performance > Stop Performance Recording. Tableau then generates a workbook with two dashboards: an overview of all events, and a detailed top-to-bottom timeline of everything that happened during your session.

  4. Rebuild the timeline to see chronology clearly 3:45

    The detailed worksheet is structured around the workbook's own layout rather than a clean timeline, so drag start index, event and worksheet onto the detail pane to reconstruct a clear chronological view of every activity and when it happened.

  5. Read the event types to see what's really happening 5:41

    Passing relates to processing the workbook's XML, connecting/executing/compiling are all query activity, and computing layout is Tableau doing the calculations for a chart without necessarily rendering it on screen — rendering events appear separately and aren't clearly tied to a specific visible or hidden zone.

  6. Hidden zones still get queried and computed upfront 6:41

    The pattern suggests Tableau runs the queries and computes the layout for all zones, including hidden ones, right at the start; only the actual rendering/drawing seems to happen when you switch to a zone. So a heavy query behind a hidden zone still loads immediately rather than waiting until you activate it.

  7. Inspect the actual SQL for debugging 8:21

    As a standalone tip, click the green query events in the recording to see the exact SQL sent to the database — useful for digging into why a particular step is slow, independent of the zone-visibility question.

Worth Knowing
  • Tim is inferring this from the recorded events, not from official Tableau documentation — he says he'll ask Tableau directly and post any semi-official answer separately.
  • Rendering events in the recording aren't clearly attributable to a specific zone, so it's hard to be certain whether hidden zones are fully rendered or just computed.
  • The demo workbook was fast to load; with a real database source you'd expect to see much larger, more obvious query sections in the recording.
Use It When

Reach for this approach when a workbook using zone visibility (or any hidden-content technique) feels slow to open, and you need to work out whether hidden sheets are silently costing you query and computation time.

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.