Em janeiro 26, 2020 13:19 Kristian Klausen via arch-mirrors escreveu:
So instead of mirroring the whole thing, the idea is to mirror only the database files (core.db etc) and download the packages on demand from a Tier 1 mirror (and let nginx cache them). By doing it that way, I only download requested packages from the Tier 1 mirrors, instead of downloading the whole thing (saving Tier 1 bandwidth).
How you actually serve the files is irrelevant to us, but it might not be irrelevant to the users, even if they don't actually *know* how you're serving files. I see some latency problems that can happen with such scenario.
Also, as pointed already, Tier 1 mirrors don't need their bandwidth saved really.
To provide even better performance a CDN (ex: Cloudflare) could be used to provide more caching. So we end up with a setup like this: Cloudflare -> Nginx cache -> Tier1 mirrors (nginx with multiple upstream)
You'll have even more latency issues for packages you have not cached yet. I wonder how are you going to do invalidatios.
Do I miss something? Is this a bad idea? If I do setup a mirror like that, is there any chance it could be added as a official mirror?
As I've said, we won't care how you serve the files. As long as you serve them and serve the right file. But users will.
Regards, Giancarlo Razzolini