From owner-freebsd-stable@freebsd.org Sun Apr 18 05:58:00 2021 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 272355F1C77 for ; Sun, 18 Apr 2021 05:58:00 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: from mail-wr1-f54.google.com (mail-wr1-f54.google.com [209.85.221.54]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FNK480XDzz4W3n; Sun, 18 Apr 2021 05:57:59 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: by mail-wr1-f54.google.com with SMTP id p6so23917123wrn.9; Sat, 17 Apr 2021 22:57:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=M3Qw5vVS3lIa1R9w55p+tTPCmXF7l3vJyl72sTJ4xto=; b=o7hBp7kexb+uYM3v/AZfeaL/b6j7nm0P3oXChxy8X5e5kKT8HIMqCaHtVVp9X4Ah4E nNHp0lg/gxRsH/efLFU1thnlZOX5DnHS+M9oxOurtHwqbd4AUVJBDDzK4XmSvRH83osG snR8NtJn8Wr9KQNaxE0qJ0Q5x20pAaGZc5hX7hZdel1dB87T57YUEkeUcwPNLESSitdf 2UTi+ihwHnUVJxQh2uatnkAEAZ6HG2dV39Q8BRCIdhIX7XiBaVWC7yCYfTJ9zONHLJlv 96JcxI6pA/013Amf517o1y+W+TWUBBEeeG8ck4d2Lvcq1eGXNcQM3k5h0lg7rox/cgnV e9TA== X-Gm-Message-State: AOAM533g9T21FtGjWNKuFnYfHaWYxeb3EVMfvuA+b3Mg0b+WhQYLNnwj VK4lBdkV1NLSWnPLPWWUJL8joKlUoxyq3yvA8KDoT2+7 X-Google-Smtp-Source: ABdhPJywx5z81rTRZseRxkzS+vA6RKAYE0LqIMNIjNq2V8EKCnZVE8HXyeN0YbvPtbjc0txad6lUHIpmpt+5Hhdx+/A= X-Received: by 2002:adf:9245:: with SMTP id 63mr7101579wrj.324.1618725477806; Sat, 17 Apr 2021 22:57:57 -0700 (PDT) MIME-Version: 1.0 References: <672990ce-2fa4-d3b0-57f1-1d3221f13e95@jku.at> <0F8B7132-0721-4999-9C3E-ED29C80BDB17@ultra-secure.de> <3c25f2c6-8686-eb29-2877-cb601c6f46bc@jku.at> In-Reply-To: From: Jason Tubnor Date: Sun, 18 Apr 2021 15:57:45 +1000 Message-ID: Subject: Re: freebsd-update and speed To: Philip Paeps Cc: Rainer Duffner , Ferdinand Goldmann , freebsd-stable , clusteradm@freebsd.org X-Rspamd-Queue-Id: 4FNK480XDzz4W3n X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Apr 2021 05:58:00 -0000 On Sun, 18 Apr 2021 at 10:51, Philip Paeps wrote: > > > It looks like there were at least experiments with pointing > freebsd-update at AWS, similar to how portsnap currently works. I will > check if these experiments went anywhere and possibly point > freebsd-update there instead. > The AWS freebsd-update has been working fine for quite a while. All project mirrors are slow in Australia so we have been using the AWS one since Colin brought it online to make it a better experience for our team to update the fleet. FWIW adjust update.FreeBSD.org to aws.update.FreeBSD.org in /etc/freebsd-update.conf and you are good to go. Can the project look at offering traditional mirrors for base and pkgs rather than the current offering? Those that want to stand up un-official mirrors can do so by pointing rsync to a Tier 2 mirror for updating purposes so they can provide faster, localised access. From Melbourne to our closest geo mirror is 240ms, this latency really drags out updates, so having a mirror out of a Melbourne DC would be beneficial. Cheers, Jason.