zozo123 commented on PR #74173: URL: https://github.com/apache/airflow/pull/74173#issuecomment-5992554113
@shahar1 — measured the current `f53486a4` design against a successful baseline with the same active job names. **Verdict: this run demonstrates useful CI savings, and supports keeping this optimization.** Both total runner time and workflow wall time improved. | Metric | Matched baseline | This PR | Improvement | |---|---:|---:|---:| | Median CI-image preparation per consumer | 210s | 127s | **83s faster (39.5%)** | | Total runner execution time | 1,306.0 min | 1,236.4 min | **69.6 runner-minutes saved (5.3%)** | | AMD workflow wall time | 51m 14s | 49m 47s | **87s faster (2.8%)** | | Median gap from CI builder completion to consumer start | 3s | 3s | No increase | **All 79 active CI-image consumers successfully restored the snapshot and skipped the legacy image-load action.** Snapshot creation took 73s and upload took 23s; the total workflow numbers above already include that 96s overhead. The critical-path tradeoff is also favorable for the median consumer in this comparison: consumers started 69s later relative to workflow creation, but their faster image preparation meant the median paired job reached the end of preparation **16s earlier**. Across all 79 paired consumers, preparation used **110.6 fewer runner-minutes**. The total workflow saving is 69.6 minutes after accounting for every executed job, including the builder. Sources: [current-head run, attempt 1](https://github.com/apache/airflow/actions/runs/37236836509) · [matched baseline run, attempt 1](https://github.com/apache/airflow/actions/runs/37267385329). Measurements use GitHub Actions job/step timestamps and consumer action outcomes. Wall time is workflow creation to the last executed job completing; runner time is the sum of executed job durations. This is one treatment run and one exact-matrix baseline, so the percentages describe this comparison rather than a guaranteed result for every PR. The dependency-layer cache saving is separate and not included as a demonstrated benefit here. Additional repetitions would establish consistency, but the measured result is already positive: **faster preparation, less runner time, and a faster completed workflow.** -- 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]
