On 8/20/2025 1:26 AM, Michael Niedermayer via ffmpeg-devel wrote:
HiIt 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.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
