From owner-freebsd-questions@freebsd.org Thu Apr 15 12:36:31 2021 Return-Path: Delivered-To: freebsd-questions@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 B53F35EE1E8 for ; Thu, 15 Apr 2021 12:36:31 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from mailout.qeng-ho.org (mailout.qeng-ho.org [217.155.128.244]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4FLf3L4wbJz3qPS for ; Thu, 15 Apr 2021 12:36:30 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from arthur.home.qeng-ho.org (unknown [IPv6:2a02:8010:64c9:1::2]) by mailout.qeng-ho.org (Postfix) with ESMTP id 865463BE73 for ; Thu, 15 Apr 2021 13:36:29 +0100 (BST) Subject: Re: Why is freebsd-update so horrible slow? From: Arthur Chance To: freebsd-questions@freebsd.org References: <2371411618364379@vla3-7c930ca38d8d.qloud-c.yandex.net> <78283e5d-f46f-2e21-7ccb-ce661531af06@qeng-ho.org> Message-ID: <78c0ba12-a8c0-a6f3-0cde-ba917519f5d3@qeng-ho.org> Date: Thu, 15 Apr 2021 13:36:29 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <78283e5d-f46f-2e21-7ccb-ce661531af06@qeng-ho.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4FLf3L4wbJz3qPS X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd@qeng-ho.org designates 217.155.128.244 as permitted sender) smtp.mailfrom=freebsd@qeng-ho.org X-Spamd-Result: default: False [-2.28 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[217.155.128.244:from]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:217.155.128.240/29:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; SUBJECT_ENDS_QUESTION(1.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[217.155.128.244:from:127.0.2.255]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.978]; DMARC_NA(0.00)[qeng-ho.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2]; ASN(0.00)[asn:13037, ipnet:217.155.0.0/16, country:GB]; MAILMAN_DEST(0.00)[freebsd-questions] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Apr 2021 12:36:31 -0000 On 15/04/2021 13:35, Arthur Chance wrote: > On 14/04/2021 02:39, Erik Lauritsen wrote: >> I have been setting here for about 6 hours waiting for an upgrade >> from 12.2 to 13 and freebsd-update is only half way through getting >> all the patches! >> >> It's painful. It's like the 90th with 56k modems and I am on a >> gigabit wire. >> >> Then I did a search and this has apparently been an issue for several >> years, it has even been filed as a bug. >> >> Anyway, I have cancelled the upgrade. If it's going to take this >> long, I am not going to upgrade this, but will most likely replace it >> with another OS. > > This tweet from Colin Percival talks about the problem. > > https://twitter.com/cperciva/status/1382491128537096193 > > TL;DR: changes to git caused a massive overload, the number of mirrors > has been increased to deal with it. > To clarify, I mean changing portsnap to use git, rather than changes in git itself. -- The number of people predicting the demise of Moore's Law doubles every 18 months.