Hello Infrastructure Team,

Apologies if I missed this, but I couldn't find it in the GitHub Actions 
Policy. I have a question about using GitHub Action runners for Apache projects.

Right now, DataFusion uses standard GitHub-provided runners, but some actions 
take a very long time (almost half an hour now, and growing). While there are 
definitely ways to improve our build times (which we are doing), some of the 
actions aren't easily optimizable and will likely require significant time now 
and even more in the future.

GitHub offers "Large" runners -- can we use them in the most resource-intensive 
workflows? Are concurrency and limits the same for those?

Thanks

Reply via email to