---
title: "Discussion on \"Power User for dbt Can Now Tell You Why Your Model Is Slow\" | Hashnode"
description: "Discussion on \"Power User for dbt Can Now Tell You Why Your Model Is Slow\". Introducing \"Profile this query\" in the Power User for dbt VS Code extension, powered by Altimate Code."
url: "https://hashnode.com/posts/power-user-for-dbt-can-now-tell-you-why-your-model-is-slow/6a6fa5f8d1dc546054c208c8"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Power User for dbt Can Now Tell You Why Your Model Is Slow](https://blog.altimate.ai/power-user-for-dbt-can-now-tell-you-why-your-model-is-slow?utm_source=hashnode&utm_medium=feed)

Introducing "Profile this query" in the Power User for dbt VS Code extension, powered by Altimate Code.

Aug 2 · 11 min read · blog.altimate.ai  
Updated Aug 9  
Read the article

-   [#dbt](https://hashnode.com/tag/dbt)
-   [#sql](https://hashnode.com/tag/sql)
-   [#sql-optimize](https://hashnode.com/tag/sql-optimize)
-   [#altimateai](https://hashnode.com/tag/altimateai)

## Written by

[Anand Gupta](https://hashnode.com/@anandgupta42)

@anandgupta42

  
[View profile](https://hashnode.com/@anandgupta42)

Co-Founder@Altimate AI

I am co-founder at Altimate AI, a start-up that is shaking up the status quo with its cutting-edge solution for preventing data problems before they occur, from the moment data is generated to its use in analytics and machine learning. With over 12 years of experience in building and leading engineering teams, I am passionate about solving complex and impactful problems with AI and ML.

## Responses 1

Markdown supported · ⌘↵ to post

[Duko tools](https://hashnode.com/@talha24ramzan)

[Aug 4](https://hashnode.com/posts/power-user-for-dbt-can-now-tell-you-why-your-model-is-slow/6a6fa5f8d1dc546054c208c8/comment/6a719614da5ad7efe8ced2a6)

The date(created\_at) example is the sharpest one, a query that filters to a single day but silently loses partition pruning because the filter function isn't sargable is exactly the kind of thing invisible from reading the SQL, but obvious the moment you see a full-table scan in the plan.

The Explain vs. Profile distinction is the right one to draw clearly, a general chatbot can describe what your SQL does, but it has no way to know your table is 3TB or that the row estimate was off by four orders of magnitude. That data only exists in the warehouse, which is the actual value-add here over pasting SQL into any LLM.