Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.project > #13916

Re: Salsa CI overload

From Ian Jackson <ijackson@chiark.greenend.org.uk>
Newsgroups linux.debian.project
Subject Re: Salsa CI overload
Date 2025-08-27 11:40 +0200
Message-ID <LokNk-aIHe-17@gated-at.bofh.it> (permalink)
References <LnLPz-ajYx-1@gated-at.bofh.it> <LoakW-aBBX-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Alexander Wirt writes ("Re: Salsa CI overload"):
> I took some statistics.

Thanks.  This is extremely illuminating.  Earlier I wrote this:

> > Perhaps some of our jobs are wasteful, but I think that overall,
> > adding capacity would be well justified.>

but these startling numbers suggest that I was wrong.

Is there any mechanism we could use for allocating capacity more
fairly?


If not, I think we must we rely on ad-hoc response to overload events,
and social pressure.  That is much less comfortable than an automatic
resource allocation system, as the latter (however imperfect) is
objective, and the message is delivered by a computer rather than an
exasperated human.

Anyway, in that case we don't want that to be a burden just on the
salsa admins, so it would be good to be able to see the numbers
publicly (at least, most of the numbers).

It should be noted of course that number of jobs is perhaps a poor
proxy for resource use, given that jobs can be of widely diffeerent
sizes.  But many jobs are so small that the overhead dominates.


> Top 5 projects today:
>   js-team/node-glob: 2751

I went and looked at this package.  I found that:

The pipeline has been failing on the main branch for some days, so it
doesn't seem like CI is being used to prevent landing broken changes
(or, it isn't effective in doing so).

I looked at one of the pipelines via the web UI and I didn't see the
thousands of jobs I was expecting based on the number above; I don't
know why.  Maybe the web UI just can't show so many.  I looked at two
arbitrary successful jobs.  They each took about 3 minutes.  Our
"docker-machine" executor container takes 1.5 minutes to set up per
job.  With small jobs like this, that time must be considered wasteful
overhead.  That's tolerable if there aren't very many.

But in this case *this project alone* has *wasted* 60 thread-hours'
worth of some kind of capacity, in a 24 hour period.  This is quite
extraordinary.

The remaining ones in the top 5, using 10x fewer jobs each, mostly
seem like repos we might expect to be under intense development.
Probably the computer resource usage there is more proportionate to
the humanm effort input.

Ian.

-- 
Ian Jackson <ijackson@chiark.greenend.org.uk>   These opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Back to linux.debian.project | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

Salsa CI overload Ian Jackson <ijackson@chiark.greenend.org.uk> - 2025-08-25 22:20 +0200
  Re: Salsa CI overload Louis-Philippe Véronneau <pollo@debian.org> - 2025-08-25 23:50 +0200
    Re: Salsa CI overload Simon Josefsson <simon@josefsson.org> - 2025-08-26 09:50 +0200
      Re: Salsa CI overload Louis-Philippe Véronneau <pollo@debian.org> - 2025-08-26 17:10 +0200
      Re: Salsa CI overload Otto Kekäläinen <otto@debian.org> - 2025-09-05 03:20 +0200
        Re: Salsa CI overload Lucas Nussbaum <lucas@debian.org> - 2025-09-05 15:40 +0200
          Re: Salsa CI overload Otto Kekäläinen <otto@debian.org> - 2025-09-05 19:40 +0200
            Re: Salsa CI overload Lucas Nussbaum <lucas@debian.org> - 2025-09-05 21:40 +0200
  Re: Salsa CI overload Alexander Wirt <formorer@debian.org> - 2025-08-27 00:30 +0200
    Re: Salsa CI overload Antoine Le Gonidec <vv221@debian.org> - 2025-08-27 01:30 +0200
      Re: Salsa CI overload Soren Stoutner <soren@debian.org> - 2025-08-27 23:50 +0200
      Re: Salsa CI overload Didier 'OdyX' Raboud <odyx@debian.org> - 2025-08-28 09:30 +0200
        salsa: unconditional rebuild of all reverse dependencies on every push considered abuse (was "Salsa CI overload") Antonio Terceiro <terceiro@debian.org> - 2025-08-28 15:00 +0200
          Re: salsa: unconditional rebuild of all reverse dependencies on every push considered abuse (was "Salsa CI overload") Jérémy Lal <kapouer@melix.org> - 2025-08-28 15:30 +0200
          Re: salsa: unconditional rebuild of all reverse dependencies on every push considered abuse (was "Salsa CI overload") Marco d'Itri <md@Linux.IT> - 2025-08-28 15:30 +0200
            Re: salsa: unconditional rebuild of all reverse dependencies on every push considered abuse (was "Salsa CI overload") Antonio Terceiro <terceiro@debian.org> - 2025-08-28 17:00 +0200
    Re: Salsa CI overload Ian Jackson <ijackson@chiark.greenend.org.uk> - 2025-08-27 11:40 +0200

csiph-web