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

   Card view requests up to 14 recent runs per DAG. The first 50 cards can 
therefore create up to 700 independent Chakra tooltip roots and state machines, 
even though only one tooltip per card can be active at a time.
   
   Reuse one multi-trigger tooltip root per DAG card. Keep every recent-run bar 
visible and clickable, and resolve the selected run's existing tooltip details 
through `Tooltip.Context` when the user focuses or hovers a trigger.
   
   Local Breeze benchmarking used 50 cards with 686 recent-run triggers across 
49 cards. Repeated cached Table-to-Card toggles measured a 907.8 ms median with 
one tooltip root per run and 825.9-859.3 ms medians with one root per card, a 
conservative 5-9% improvement. The 686 triggers now use 49 tooltip controllers.
   
   This is an incremental reduction in Card-view render work, not a claim that 
it removes the full delay reported in the issue.
   
   No visual change is expected, so before/after screenshots are not applicable.
   
   related: #69609
   
   Testing:
   
   - `pnpm exec vitest run src/pages/DagsList/DagCard.test.tsx`
   - `pnpm exec tsc --p tsconfig.app.json --noEmit`
   - `pnpm exec eslint src/pages/DagsList/RecentRuns.tsx 
src/pages/DagsList/DagCard.test.tsx`
   - `pnpm build`
   - `uvx prek run --files 
airflow-core/src/airflow/ui/src/pages/DagsList/RecentRuns.tsx 
airflow-core/src/airflow/ui/src/pages/DagsList/DagCard.test.tsx`
   - Playwright hover verification against a local Breeze instance
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (Codex)
   
   Generated-by: Codex following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   


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