GitHub user potiuk closed the discussion with a comment: Request: reduce the 
amount of time used on Apache shared runners

Thanks for this issue - it is absolutely what we are doing now. In case you 
have not noticed we are well in the process of doing just that (and already 
implemented some of earlier - easier optimisations). I thin everyone (including 
@hubcio and @alamb in your projects) - you should have similar approach we do - 
where we, proactively - before issues like that - plan and relentlessly execute 
optimizations efforts. 

I would really love if all the projects do that - including those projects 
which experienced the queuing time now. Everyone's small optimisation count, 
and I hope Airflow blueprinit on how to do that might be followed.

All of the optimizations we tried and plan are also described in this PR to the 
infra website - https://github.com/apache/infrastructure-website/pull/320  
where we share and ask others to try similar things.


* https://github.com/apache/airflow/pull/74825 and 
https://lists.apache.org/thread.html/nfno4r1jqx5dj75v867prjjgg6o77odx and 
https://cwiki.apache.org/confluence/spaces/AIRFLOW/pages/451974711/AIP-120+Run+CI+for+external+contributions+in+contributor+forks
 

* https://github.com/apache/airflow/pull/74889 tha - 
https://lists.apache.org/thread.html/lfgvvffhtzgpbyy3dm197vftsg448qpx and  
https://cwiki.apache.org/confluence/spaces/AIRFLOW/pages/451974652/AIP-118+Self-hosted+runners+for+Apache+Airflow+CI
 

My estimate is that it will reduce Airflow usage by about 80% overall.

Let me close the issue - because it's been outdated before it's been opened.



GitHub link: 
https://github.com/apache/airflow/discussions/75395#discussioncomment-19121712

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to