From: "'Heinisch, Alexander' via isar-users" <isar-users@googlegroups.com>
To: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: RE: Reliability and build time improvements with apt-cacher-ng
Date: Tue, 3 Sep 2024 08:34:42 +0000 [thread overview]
Message-ID: <AM7PR10MB3320404898398C78E8231FC786932@AM7PR10MB3320.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <4ec252e79e1bffaee0b6403150a26fc1c1ea2517.camel@siemens.com>
> > Hi Felix!
> >
> > > I just played around with apt-cacher-ng to circumvent the throttling
> > > issues on snapshots.d.o, and got some impressive results:
> >
> > We just migrated our gitlab-runners (for a downstream project based on
> > isar-cip-core) to a new build server.
> > The project builds 4 images (all for amd64 arch) whereas 2 of them are
> > done in a multiconfig setup using the isar-installer.
> > In total the complete build fetches 423MB of apt packages from
> > snapshot-cloudflare.debian.org
>
> Please note, that snapshot-cloudflare stopped mirroring in June. The only official debian snapshot mirror is snapshot.debian.org, and there we have massive problems with rate limiting.
>
> For more details, please also see "[PATCH 1/1] switch debian snapshot mirror to snapshot.debian.org".
Thanks for the hint!
The rate limiting was the reason to switch to cloudflare mirror in the first place.
Currently, we are on a snapshot preceding the current cloudflare limitation, but
we will upgrade in the next weeks when preparing for the next release.
I never experienced the rate limiting outside our corporate network.
That way, maybe, rate limiting won't hit us that hard, when using the cache in our ci/cd.
What do you think of hosting snapshot mirrors for isar based projects (or others) on our own?
BR Alexander
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/AM7PR10MB3320404898398C78E8231FC786932%40AM7PR10MB3320.EURPRD10.PROD.OUTLOOK.COM.
prev parent reply other threads:[~2024-09-03 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AQHa3ec4qROUDTPcc02+hYB7aqyKvg==>
2024-07-24 16:33 ` 'MOESSBAUER, Felix' via isar-users
2024-08-22 11:10 ` 'Alexander Heinisch' via isar-users
2024-09-03 7:26 ` 'MOESSBAUER, Felix' via isar-users
2024-09-03 8:34 ` 'Heinisch, Alexander' via isar-users [this message]
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=AM7PR10MB3320404898398C78E8231FC786932@AM7PR10MB3320.EURPRD10.PROD.OUTLOOK.COM \
--to=isar-users@googlegroups.com \
--cc=alexander.heinisch@siemens.com \
--cc=felix.moessbauer@siemens.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox