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

   Closes: #70018 
   
   ### Description
   
   ### Motivation
   
   Improves the performance of the scheduler loop by optimizing 
[ConcurrencyMap.load](file:///home/rajat/airflow/airflow-core/src/airflow/jobs/scheduler_job_runner.py#L239-L247).
 By introducing a composite index on `(state, dag_id, task_id, run_id)` inside 
[taskinstance.py](file:///home/rajat/airflow/airflow-core/src/airflow/models/taskinstance.py),
 we enable a **Covering Index Scan** (Index Only Scan) and eliminate the 
temporary B-Tree sorting/grouping step when aggregating active task instances.
   
   ### Proposed Changes
   
   1. **Model Update**: Added index definition to `TaskInstance.__table_args__` 
in 
[taskinstance.py](file:///home/rajat/airflow/airflow-core/src/airflow/models/taskinstance.py):
      ```python
      Index("ti_state_active_composite", state, dag_id, task_id, run_id)
      ```
   2. **Database Migration**: Added an Alembic migration script to create 
`ti_state_active_composite`.
   
   ### Verification
   
   Ran query plan analysis and benchmarks on SQLite:
   * **Before Plan**:
     ```text
     SEARCH task_instance USING INDEX ti_state (state=?)
     USE TEMP B-TREE FOR GROUP BY
     ```
   * **After Plan**:
     ```text
     SEARCH task_instance USING COVERING INDEX ti_state_active_composite 
(state=?)
     ```
   * **Performance Gain**: ~10% latency reduction on local SQLite; expected to 
be higher under high PostgreSQL/MySQL heap-read and buffer pool pressure.
   
   
    <!-- SPDX-License-Identifier: Apache-2.0
         https://www.apache.org/licenses/LICENSE-2.0 -->
   
   <!--
   Thank you for contributing!
   
   Please provide above a brief description of the changes made in this pull 
request.
   Write a good git commit message following this guide: 
http://chris.beams.io/posts/git-commit/
   
   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.
   
   For user-facing UI changes, please attach before/after screenshots (or a 
short
   screen recording) so reviewers can assess the visual impact.
   
   Feel free to ping (in general) for the review if you do not see reaction for 
a few days
   (72 Hours is the minimum reaction time you can expect from volunteers) - we 
sometimes miss notifications.
   
   In case of an existing issue, reference it using one of the following:
   
   * closes: #ISSUE
   * related: #ISSUE
   -->
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   <!--
   If generative AI tooling has been used in the process of authoring this PR, 
please
   change below checkbox to `[X]` followed by the name of the tool, uncomment 
the "Generated-by".
   -->
   
   - [x] Yes (please specify the tool below)
   Gemini Pro 3.1
   
   <!--
   Generated-by: [Tool Name] following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   -->
   
   ---
   
   * Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information. Note: commit author/co-author name and email in commits 
become permanently public when merged.
   * For fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   * When adding dependency, check compliance with the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: 
`{pr_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
 You can add this file in a follow-up commit after the PR is created so you 
know the PR number.
   


-- 
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]

Reply via email to