I just installed apt cacher ng for catching my apt upgrade packages and saw a huge time improvement even though I have a good internet connection. It act as a proxy and caches the response packages.

Do you run something similar? Or maybe even run a local repo mirror? Warning, they are really big so I don’t think it is recommended unless you really need almost everything.

  • vegetaaaaaaa@lemmy.worldEnglish
    2·
    1 year ago

    I want to look into apt-cacher-ng for learning purposes, to stop 10s of VMs in my homelab from adding load to Debian official repos, and also to check if there is a way to have it only mirror a list of “approved” packages.

    saw a huge time improvement even though I have a good internet connection

    Note that for best performance you should use https://deb.debian.org/

    Semi-related I have set up a personal APT repository on gitlab pages: https://nodiscc.gitlab.io/toolbox/ (I think Ubuntu users would call that a “PPA”). It uses aptly and a homegrown Makefile/Gitlab CI-based build system (sources/build tools are linked from the page). I wouldn’t recommend this exact setup for critical production needs, but it works.

      • Mio@feddit.nuOPEnglish
        1·
        1 year ago

        The dvds are fine for offline use. But I dont know how to keep them updated. Probably result in taking loads of spaces as I guess they are equal to a repo mirror

    • Mio@feddit.nuOPEnglish
      2·
      1 year ago

      I use it with Kubuntu. Doing apt update is now much faster. I did some testing and found some good public mirror so I could max my connection(100 Mbit) with about 15ms latency to the server. But I think the problem was there are so many small files. Running nala to fetch the files in parallel helps of course. With apt local ng I don’t need nala at all. The low latency and files on gigabit connection to my server leads to fast access. Just need to find a good way to fill it with new updates.
      A second problem is to figure out if something can be done to speed up the apt upgrade, which I guess is not possible. Workaround with snapshots and send diff does not sound efficient either, even on older hardware.

      apt update - 4 seconds vs 16 seconds.

      apt upgrade --download-only - 10 seconds vs 84 seconds;