Hi,

Reviewing the picture today, the GitHub hosted runners utilisation overall is 
still maxxing out daily. WIth respect to flink we can see over the last 7 days 
that the project has dropped out of the top 5 to 10 which is good progress. 
Your continued work and vigilance on this area helps all projects and is 
appreciated.

Please note that there is now a page for sharing tips and best practice for 
optimising workflows with respect to utilisation:

https://cwiki.apache.org/confluence/display/INFRA/GitHub+Actions+Recommended+Practices

There is also a Slack channel for community discussion and sharing ideas: 
project-workflow-optimisations

Thanks.

Kind regards,
-Bob Thomson,
ASF Infrastructure

On 2026/05/26 15:30:33 Robert Metzger wrote:
> Thanks for looking into this.
> 
> I agree reducing the frequency of flink-ml related builds massively.
> 
> On Tue, May 26, 2026 at 11:47 AM Sergey Nuyanzin <[email protected]>
> wrote:
> 
> > Thanks for letting us know Robert.
> >
> > After looking at the report I noticed 2 things
> > 1. Flink nightlies on the first place (I turned off them for 2.1 and
> > 2.2 in GHA) [1]
> > 2. In the second place (if shown for the last 7 days) there are
> > "Python Tests" and also "Java Tests" in top10, both are from Flink-ml
> > repo [2]
> > Flink-ml was not updated within the last 2 years... Thus I would
> > propose to change nightlies for this repo from every night to every
> > month
> >
> >
> > [1] https://issues.apache.org/jira/browse/FLINK-39734
> > [2] https://github.com/apache/flink-ml/tree/master/.github/workflows
> >
> > On Fri, May 22, 2026 at 1:47 PM Robert Thomson <[email protected]>
> > wrote:
> > >
> > > Hello, Flink PMC.
> > >
> > > In 2024, the ASF introduced the policy for GitHub Actions usage
> > > across the foundation[1]. 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 and this is the
> > > case again today.
> > >
> > > Your project has been identified as being among the top 5 consumers of
> > > build time over the past 7 days and we request that you bring your
> > > usage down by stream-lining long-running builds. Contact Infra for
> > > a consultation if you are unable to streamline your builds further.
> > >
> > > You can use the infra reporting tool[2] to monitor your GHA usage as you
> > > work on stream-lining, as well as locate any bottlenecks in the
> > workflows.
> > >
> > > Infra will allow you two weeks time (till the 8th of June, 2026) to
> > > progress this, but should you still be above the limits by then,
> > > without a viable path forward, we will be limiting your GHA usage.
> > >
> > > 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&project=flink&hours=24&limit=15&group=name
> >
> >
> >
> > --
> > Best regards,
> > Sergey
> >
> 

Reply via email to