M
markatdataandbeyond/dbu-waste-finder
A free, read-only Databricks notebook that shows where your DBUs go and which resources look wasteful, using only
更新 2026-10-30
在 GitHub 查看 ↗直链 · 无中转页
我们没有从该仓库取到可核对的安装命令,也没有公开的远端端点。这两样都没有时,我们不出配置——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 0 ★ · markatdataandbeyond/dbu-waste-finder · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
markatdataandbeyond/dbu-waste-finder;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# DBU Waste Finder
以下摘录自该仓库的 README(片段)
A free, read-only Databricks notebook that shows where your DBUs go and which resources look wasteful, using only
Databricks system tables. One notebook, no install; the notebook sends nothing out of your workspace.
This repo contains two things:
notebook/ – the free notebook (below).
mcp/ – an MCP server so Claude/Cursor can answer "why did our bill jump?" from your system tables and propose fixes as a diff to your Asset Bundle (read-only, never applied). See mcp/README.md.
Landing page: https://markatdataandbeyond.github.io/dbu-waste-finder/
## What it checks
| Check | Source tables |
| Cost by product and top 20 cost drivers (jobs, warehouses, clusters) at list price | system.billing.usage + system.billing.list_prices |
| Jobs running on all-purpose compute, with the list-price difference to job compute (ratio from the cluster's own billed SKU and cloud in list_prices; on a shared cluster only the share of billed time used by job runs counts, the full figure is shown as est_saving_upper_bound_usd) | system.lakeflow.job_task_run_timeline (compute_ids), system.compute.clusters |
| All-purpose clusters with auto-termination off (0/NULL) or above 60 min, incl. clusters deleted inside the window | system.compute.clusters (latest SCD row) |
| Idle or oversized clusters (avg CPU =3 days, have 0.23".
low_confidence: true (plus a note) when observation_days < 7 (3–7 days: projection shown but flagged). Exactly 7 is not flagged.
This is an extrapolation of past waste at list price, not a promise of what you will get back.
## Demo output (example data)
The snippet below is example / fixture data, not a live workspace. It was produced by running the MCP tools
(cost_summary, top_cost_drivers, find_waste, propose_fix) against the same mock system-table rows the
unit tests use.
text
cost_summary(days=15)
total_list_cost_usd: 1000.00 (JOBS 700 + ALL_PURPOSE 300; usd_complete=false, GENIE_FREE_USAGE unpriced)
daily: 2026-10-01 → $33.30
top_cost_drivers(days=15)
job etl-nightly $500.00
cluster c-shared-01 $300.00
warehouse wh-sql-01 $120.00
find_waste(days=15)
measured_saving_usd: 203.15 measured_waste_dbu: 4.5
observation_days: 15.0 projected_30d_usd: 406.30
jobs_on_all_purpose: c-shared-01 (2 jobs, est. $165 if moved to job compute)
missing_autotermination: c-adhoc-02 (auto_termination_minutes=0)
idle_or_oversized: c-idle-03 (CPU 4 %, mem 12 %, est. $35)
idle_warehouse: wh-sql-01 (98.4 % idle, 4.0 DBU → $2.80)
delta_needs_optimize: main.bronze.events (500 files, ~4 MiB avg)
delta_needs_vacuum: main.bronze.events (40 days since vacuum, ~3 GiB reclaimable)
delta_overfrequent_optimize: main.silver.orders (14 OPTIMIZE runs / 7 days)
propose_fix(issue="delta_optimize", resource_key="main.bronze.events")
-- Proposal only; review before running. DBU Waste Finder never executes this.
OPTIMIZE main.bronze.events;
## Live trial run (real workspace, 2026-10-29)
Not fixture data. Same tools (cost_summary, top_cost_drivers, find_waste, cost_review_report) against a Databricks trial workspace over serverless SQL (Statement API + system tables only).
| Field | Value |
| Observed days | 2.84 (30-day lookback requested) |
| Total list-price cost | $18.17 (usd_complete: false — GENIE_FREE_USAGE 0.326 DBU unpriced) |
Databricks system tables. One notebook, no install; the notebook sends nothing out of your workspace.
This repo contains two things:
notebook/ – the free notebook (below).
mcp/ – an MCP server so Claude/Cursor can answer "why did our bill jump?" from your system tables and propose fixes as a diff to your Asset Bundle (read-only, never applied). See mcp/README.md.
Landing page: https://markatdataandbeyond.github.io/dbu-waste-finder/
## What it checks
| Check | Source tables |
| Cost by product and top 20 cost drivers (jobs, warehouses, clusters) at list price | system.billing.usage + system.billing.list_prices |
| Jobs running on all-purpose compute, with the list-price difference to job compute (ratio from the cluster's own billed SKU and cloud in list_prices; on a shared cluster only the share of billed time used by job runs counts, the full figure is shown as est_saving_upper_bound_usd) | system.lakeflow.job_task_run_timeline (compute_ids), system.compute.clusters |
| All-purpose clusters with auto-termination off (0/NULL) or above 60 min, incl. clusters deleted inside the window | system.compute.clusters (latest SCD row) |
| Idle or oversized clusters (avg CPU =3 days, have 0.23".
low_confidence: true (plus a note) when observation_days < 7 (3–7 days: projection shown but flagged). Exactly 7 is not flagged.
This is an extrapolation of past waste at list price, not a promise of what you will get back.
## Demo output (example data)
The snippet below is example / fixture data, not a live workspace. It was produced by running the MCP tools
(cost_summary, top_cost_drivers, find_waste, propose_fix) against the same mock system-table rows the
unit tests use.
text
cost_summary(days=15)
total_list_cost_usd: 1000.00 (JOBS 700 + ALL_PURPOSE 300; usd_complete=false, GENIE_FREE_USAGE unpriced)
daily: 2026-10-01 → $33.30
top_cost_drivers(days=15)
job etl-nightly $500.00
cluster c-shared-01 $300.00
warehouse wh-sql-01 $120.00
find_waste(days=15)
measured_saving_usd: 203.15 measured_waste_dbu: 4.5
observation_days: 15.0 projected_30d_usd: 406.30
jobs_on_all_purpose: c-shared-01 (2 jobs, est. $165 if moved to job compute)
missing_autotermination: c-adhoc-02 (auto_termination_minutes=0)
idle_or_oversized: c-idle-03 (CPU 4 %, mem 12 %, est. $35)
idle_warehouse: wh-sql-01 (98.4 % idle, 4.0 DBU → $2.80)
delta_needs_optimize: main.bronze.events (500 files, ~4 MiB avg)
delta_needs_vacuum: main.bronze.events (40 days since vacuum, ~3 GiB reclaimable)
delta_overfrequent_optimize: main.silver.orders (14 OPTIMIZE runs / 7 days)
propose_fix(issue="delta_optimize", resource_key="main.bronze.events")
-- Proposal only; review before running. DBU Waste Finder never executes this.
OPTIMIZE main.bronze.events;
## Live trial run (real workspace, 2026-10-29)
Not fixture data. Same tools (cost_summary, top_cost_drivers, find_waste, cost_review_report) against a Databricks trial workspace over serverless SQL (Statement API + system tables only).
| Field | Value |
| Observed days | 2.84 (30-day lookback requested) |
| Total list-price cost | $18.17 (usd_complete: false — GENIE_FREE_USAGE 0.326 DBU unpriced) |
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/markatdataandbeyond-dbu-waste-finder/)
- 来源
- awesome · https://github.com/markatdataandbeyond/dbu-waste-finder
- 按领域浏览
- MCP 服务
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。