From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: Re: [FFmpeg-devel] CI
Date: Wed, 20 Aug 2025 21:25:02 +0200
Message-ID: <20250820192502.GC29660@pb2> (raw)
In-Reply-To: <5ee0b9e5-935c-4264-a6db-a66cfcf7ae3a@rothenpieler.org>
[-- Attachment #1.1: Type: text/plain, Size: 2010 bytes --]
Hi
On Wed, Aug 20, 2025 at 05:56:27PM +0200, Timo Rothenpieler via ffmpeg-devel wrote:
> On 8/20/2025 1:26 AM, Michael Niedermayer via ffmpeg-devel wrote:
> > Hi
> >
> > It seems the forgejo CI takes about
> > 13min to do fate on aarch64 and x86-64 and build on win64
> >
> > Locally i run
> > fate + install on x86-64
> > build on x86-32, mingw64, arm32, mips, ppc, x86-64 + shared libs
> > testprogs alltools examples build on x86-64, x86-32 and arm32
> > in 2min 44sec
> >
> > can we improve the speed vs amount of tests ratio ?
> > (its not a problem ATM, i did in fact not even notice as i never waited on it)
> >
> > Iam just seeing the difference in time and i think there is potential for
> > optimization here
> >
> > I dont think my box here is really special, just a
> > AMD Ryzen 9 3950X 16-Core + Samsung SSD 970 PRO
>
> Well, the test runners are 4 cores and 8GB of RAM. So that'll be the primary
> difference in speed.
> I think they're performing pretty good for being just that.
>
> We could of course throw money at the problem and turn them into 16 core
> machines. That would up the hosting cost of the runners from currently
> 3*7.5€ a month to 3*30€ a month. Just for the runners.
>
> imo the current CI turnaround times are fine. 15-20 minutes per job is fine,
> as long as they can all run in parallel.
Option 1: 15-20 min CI turnaround, 270 € per year
Option 2: 4-5? min CI turnaround, 1080 € per year
we have over 150k $ it seems
Good use of capital can also lead to more donations
I think the main question is, "would we benefit from the faster trunaround"?
or not ?
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
If the United States is serious about tackling the national security threats
related to an insecure 5G network, it needs to rethink the extent to which it
values corporate profits and government espionage over security.-Bruce Schneier
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-08-20 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 23:26 Michael Niedermayer via ffmpeg-devel
2025-08-20 15:56 ` Timo Rothenpieler via ffmpeg-devel
2025-08-20 19:25 ` Michael Niedermayer via ffmpeg-devel [this message]
2025-08-20 22:31 ` Timo Rothenpieler via ffmpeg-devel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250820192502.GC29660@pb2 \
--to=ffmpeg-devel@ffmpeg.org \
--cc=michael@niedermayer.cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git