> Is it enough for now? I'm not from ASF Infra. But here's what we use to evaluate against our resource usage for Iceberg.
https://infra.apache.org/github-actions-policy.html - The average number of minutes a project uses per calendar week MUST NOT exceed the equivalent of 25 full-time runners (250,000 minutes, or 4,200 hours). - The average number of minutes a project uses in any consecutive five-day period MUST NOT exceed the equivalent of 30 full-time runners (216,000 minutes, or 3,600 hours). For Arrow: Past 7 days: Total usage: 146,826 minutes https://infra-reports.apache.org/#ghactions&project=arrow&hours=168&limit=15&group=name Past 5 days: Total usage: 86,611 minutes https://infra-reports.apache.org/#ghactions&project=arrow&hours=120&limit=15&group=name On Tue, Jun 23, 2026 at 6:51 PM Sutou Kouhei <[email protected]> wrote: > Hi, > > We've reduced our CI usage from 198,402 minutes to 146,106 > minutes (73%): > > https://github.com/apache/arrow/issues/50169#issuecomment-4785153675 > > Is it enough for now? > > Thanks, > -- > kou > > In <[email protected]> > "Re: Consumption of ASF Shared GitHub-hosted Runner Resources" on Mon, > 15 Jun 2026 06:06:09 +0900 (JST), > Sutou Kouhei <[email protected]> wrote: > > > Hi, > > > > Thanks for sharing them. > > > > I've opened https://github.com/apache/arrow/issues/50169 to > > track our work. > > > > > > Thanks, > > -- > > kou > > > > In <cafrfahpqhxkc0gx_0anc8+nonkf92biko40rxdz+r_bchxl...@mail.gmail.com> > > "Consumption of ASF Shared GitHub-hosted Runner Resources" on Fri, 12 > Jun 2026 14:51:39 +0200, > > Robert Thomson <[email protected]> wrote: > > > >> Hi, > >> > >> In 2024, the ASF introduced the policy for GitHub Actions usage across > >> the foundation[1]. As you have likely experienced, the ASF Github > >> shared pool of Github-hosted runners has been at, or very close to the > >> limit of 900 jobs most of the time in the past few weeks, causing jobs > >> to queue for lengthy periods before running. > >> > >> Your project has been identified as being among the top consumers of > >> build time over the past 7 days and we request that you make efforts > >> to bring your usage down by stream-lining long-running builds and > >> minimising the number of concurrent builds. > >> > >> You can use the infra reporting tool [2] to monitor your GHA usage as > you > >> work on stream-lining and to locate any bottlenecks in the workflows. > >> > >> There is now on-going community discussion on a Slack channel, > >> “project-workflow-optimisations” about the topic of optimising GitHub > >> Actions workflows so as to minimise both the number of concurrent jobs > >> running on our limited allocation, and the number of long-running > >> jobs. > >> > >> To share best practices between projects on this area we encourage > >> projects to contribute to this cwiki page: > >> > >> > https://cwiki.apache.org/confluence/display/INFRA/GitHub+Actions+Recommended+Practices > >> > >> It is also possible for a project to maintain their own self-hosted > >> runners if they can provide a suitable VM/on-prem hardware to execute > >> the runner: > >> > >> > https://cwiki.apache.org/confluence/display/INFRA/GitHub+self-hosted+runners > >> > >> Kind regards, > >> Bob Thomson, on behalf of ASF Infrastructure. > >> > >> > >> [1] https://infra.apache.org/github-actions-policy.html > >> [2] https://infra-reports.apache.org/#ghactions >
