---
title: "Comment by StockPearl on \"How IFCO Cut a 7-Hour dbt Job to 2 Hours 20 Minutes on Databricks\" | Hashnode"
description: "The window sizing tradeoff is the part I've struggled with too. On a filings dataset I work on, corrections can show up months later when a company amends a rep"
url: "https://hashnode.com/posts/how-ifco-cut-a-7-hour-dbt-job-to-2-hours-20-minutes-on-databricks/6af3681b5454f0d485c2adb9/comment/6af3fd454d90c3845e288fd7"
---

[Discussion](https://hashnode.com/posts/how-ifco-cut-a-7-hour-dbt-job-to-2-hours-20-minutes-on-databricks/6af3681b5454f0d485c2adb9)

Comment [How IFCO Cut a 7-Hour dbt Job to 2 Hours 20 Minutes on Databricks](https://hashnode.com/posts/how-ifco-cut-a-7-hour-dbt-job-to-2-hours-20-minutes-on-databricks/6af3681b5454f0d485c2adb9)

[StockPearl](https://hashnode.com/@stockpearl)

[20h ago](https://hashnode.com/posts/how-ifco-cut-a-7-hour-dbt-job-to-2-hours-20-minutes-on-databricks/6af3681b5454f0d485c2adb9/comment/6af3fd454d90c3845e288fd7)

The window sizing tradeoff is the part I've struggled with too. On a filings dataset I work on, corrections can show up months later when a company amends a report, so a fixed lookback either misses them or rescans far too much. What helped was keying reconciliation off what actually changed upstream instead of a date window. Curious whether IFCO's late events had a hard upper bound on lateness, or if the window was picked from observed data.