Every dvt operation journals itself — live records, heartbeats, outcomes — in .dvt/executions/. A run that dies silently shows up here as STALE, never as live.
Loading…
A single duration says little. These are the phases and models that cost the most across recent operations — where to look first when the project got slower.
Loading…
dbt children, sling shims and their Go children, with CPU and RAM. Orphans — dvt-owned slings whose owner died — are flagged red; the next dvt operation's startup sweep reaps them.
Loading…
Loading…
Loading…
Each operation samples its own tmp and staging footprint while it works and keeps the PEAK — so a run that ballooned mid-flight and cleaned up after itself still shows here.
Loading…
Loading…
Loading…
Loading…
Loading…