You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The event telemetry dbt models take a long time to rebuild every night, one particular model unstruct_event_flattened blocks everything downstream for almost an hour. We can easily make these speed up by using incremental models.
Its not an immediate issue since we only use an x-small warehouse so the cost is low and we only refresh once a day but it would hugely benefit the days where we need to rerun failed jobs, or refresh after a deployment.
The text was updated successfully, but these errors were encountered:
To follow up on this - it ended up leading to a 38% decrease in runtime. So its completes in ~75 mins vs 120. Which is ~22.5 hrs a month @ $6 per hour = $135 per month savings.
The total node runtime increase by about 5 mins but the parallelization allowed the queries to distribute better and optimize the available threads better. Theres still more incremental logic we can add to reduce this further but this is a good start.
The event telemetry dbt models take a long time to rebuild every night, one particular model
unstruct_event_flattened
blocks everything downstream for almost an hour. We can easily make these speed up by using incremental models.Its not an immediate issue since we only use an x-small warehouse so the cost is low and we only refresh once a day but it would hugely benefit the days where we need to rerun failed jobs, or refresh after a deployment.
The text was updated successfully, but these errors were encountered: