potiuk opened a new pull request, #38107:
URL: https://github.com/apache/airflow/pull/38107

   This is another step of decomposing our workflows and introducing more DRY 
approach for GitHub Actions workflows we have. Building cache started to take 
more time and space as we started to build 5 images at the same time with 
Python 3.12 inclusion, so optimizing the builds now is a good idea.
   
   There are several optimizations here:
   
   1) Instead of building images in parallel on bigger instances, we
      rather choose to start small ARM instances with less CPUs but
      build one image per instance. This will make them generally
      faster with the same price (less contention) at the expense
      of using more AMD instances to drive them
   
   2) However we also make sure to build both AMD and ARM cache at
      the same time in parallel - the AMD on the driving AMD instance and
      the ARM on the ARM instance. This will make the AMD instances also
      busy while ARM instance is building their images - and AMD instance
      will be finishing faster in general rather than waiting for all the
      5 images to complete.
   
   In order to accomplish it we change the parallelism model when the 
`--prepare-buildx-cache` command is used - instead of parallelising with python 
versions we parallelise with the platforms, which allows to run both AMD and 
ARM image in parallel.
   
   This change also removes building ARM image in build-images step as it is 
not really needed for anything - we already do such build in the CI workflow 
and builing it again in "build images" workflow is superfluous.
   
   Builds on changes implemented in #37865 and #38057
   
   <!--
    Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file
    distributed with this work for additional information
    regarding copyright ownership.  The ASF licenses this file
    to you under the Apache License, Version 2.0 (the
    "License"); you may not use this file except in compliance
    with the License.  You may obtain a copy of the License at
   
      http://www.apache.org/licenses/LICENSE-2.0
   
    Unless required by applicable law or agreed to in writing,
    software distributed under the License is distributed on an
    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
    KIND, either express or implied.  See the License for the
    specific language governing permissions and limitations
    under the License.
    -->
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of an existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   
   
   <!-- Please keep an empty line above the dashes. -->
   ---
   **^ Add meaningful description above**
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in a 
newsfragment file, named `{pr_number}.significant.rst` or 
`{issue_number}.significant.rst`, in 
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
   


-- 
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: commits-unsubscr...@airflow.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to