Sonsum wrote: ketoth wrote:
To get closer to the main subject: as you can imagine when UP5 will be released it will be quite a chaos (very slow download speed, even server downtime). So I'm coming back with my BitTorrent idea (providing repository mirror maintainers with the full update pack in a torrent, then a "touch-script" clearing the modtimes to ensure rsync won't redownload all the mess). Now is a good time to test it, and now is also a good time to build a repository mirror, especially if you want to be from the "incoming" testers. Contact me if you need more information
If this isn't being implemented, this would be a great idea and one that I also just thought of. I just downloaded the latest version of Libreoffice through a torrent from the main site and the speed is incredible. Now that BitTorrent has included Web Seeds, a server can act as a torrent peer. This means that the torrent will always be active and almost always faster than a HTTP download. Not to mention a dramatic reduction in bandwidth for the server. I'd prefer to get my UP5 in a torrent!
Not really the point for the end user I guess, unless you want to stuff about 266 GB of data in your APT cache
There is apt-p2p who could help for big packages (like game data, LibreOffice,..), but initiating P2P exchange for every single little library package is very slow.
According to my tests it COULD be possible with a unique torrent and build an updater who "picks" the files it needs for this torrent: the torrent file itself weights about 30 MB (and most BitTorrent clients I tested couldn't correctly parse the content, too many files I guess). Once the package selection made, the updater could retrieve them through webseeds. Using a constant BitTorrent transfer would be problematic, some people don't want BitTorrent daemons running permanently on their pc and/or do have limited and metered bandwidth.
Anyway starting now the repository mirroring uses a pool-based system: 2 folders, one for latest, one for incoming (a symlink makes them accessible through /latest and /incoming). Once the UP5 ready, repository mirrors won't have to rsync the full archive while everybody else wants to upgrade: just a quick rsync to update the symlink to point to the other pool, and voilà
The issue now is that these repository mirrors, to be useful in reducing the server load on the main sever, actually have to be.. used. For example during the mintinstall the user could be asked if he wants only the main server or wants to add geographically close servers to his sources.list (with a correct pinning so the main server is used only as a fallback in case of mirror downtime). And: the Mint team is setting up additional servers so the upgrade will be as smooth as possible for everybody