zozo123 commented on PR #74311: URL: https://github.com/apache/airflow/pull/74311#issuecomment-6254494755
Measurements from the last four scheduled `main` AMD canaries: 38993077423, 39038765293, 39088484466 and 39133923075. They come from job timestamps and from the per-row timestamps in the `Deps` step logs. | per canary | | |---|---| | canary wall clock today | 172–215 min | | without the explanations (estimate) | 79–114 min, i.e. 92–108 min shorter | | explanation work that moves to the report | 438–515 runner-min across the 12 `Deps` jobs | | report overhead on top of that | about 12 × 4–6 min = 50–70 runner-min (checkout, disk cleanup, image download and load) | **How I estimated it:** - The check prints one table row per package and computes each outdated package's explanation inline, before printing that row. - So the time between rows for up-to-date packages is just the lookup: 0.03–0.11 s per row, or 0.4–1.5 min for about 800 packages. The rest of the step is explanation. - Today the canary ends with the slowest `Deps …:constraints-source-providers` job. The last job that isn't a `Deps` job finishes 93–109 min earlier, so almost all of that time comes off the canary. **Result:** the canary gets about 1.5 h shorter. The net cost is roughly 50–70 extra runner-minutes per canary for the report's setup. The report runs three jobs at a time, so it takes longer in wall clock, but that time is off the canary's path. **One fix this turned up:** the 90-minute job limit was too low. The constraints-source-providers jobs take 105–120 min, up to 115 min of which is explanation. a505227ff4 raises the limit to 150 min and updates the docs. _🤖 Addressed by [Claude Code](https://claude.com/claude-code)_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
