From nobody Wed Mar 29 10:44:22 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Pmjpz2pkXz42NMm for ; Wed, 29 Mar 2023 10:44:27 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 4Pmjpy4xKbz40kq for ; Wed, 29 Mar 2023 10:44:26 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b=SwmZVuXj; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=XG0FeIQc; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.26 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 17D415C00DA for ; Wed, 29 Mar 2023 06:44:26 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Wed, 29 Mar 2023 06:44:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm2; t=1680086666; x=1680173066; bh=t1 /RTaj9e8AJxEnBeFvcxrtZwlGM7No76GEnFOKMsIo=; b=SwmZVuXjEXpIXfT1qE ol6FjJGGfMWheeXCcx0dbFbD67VoOJ02ZOAGDgoRKGHwfAyoJ0GAyLl207HZ4UcW 63YcbYf0QJKZHzfcbtI/WLUOAijyGN4DZ1Ir/4e/V/UZgMOYLjQZiK7zoR5xtyrF E6bespA9nV6SBI9HhPduL71ZePPD5Y8JdMJtIHzwA2u6gsWP51WpVkZDktycuMBv PGvLONxj0w9TXS5mzvZ3TygD7jjDzhwq/QNqUuFVLW7jUGvIhrusc3lzC3aDFTOV 9jpshSUl5SCUoDTjLrRM62xFj/NwFu5/OHRGT+HbK6u604Grx1EIFaUNSD1pNJtY 5l5A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; t=1680086666; x=1680173066; bh=t1/RTaj9e8AJx EnBeFvcxrtZwlGM7No76GEnFOKMsIo=; b=XG0FeIQcCh5mYeW5+jF4dOVVb3jQm 3ys215/8NP1sE86/k7fYqBEa3PqKMPn59Pf7c1dsHSjQQH6jgJkPVZFb5NOFvY78 EdWOaV4p55VeeLhJxVCJrcZOCfKRtNwpMIsqbbmrdvs0/0fmQFqBXWe4limybPtM EpGz87AlPqPap79/NZ55CFxdzkFQnRVT/RhN1xcAJaHbhlLvsdl9rVvn4bRNZpwG hFmwnFeGFrz2Gkm0qHSmHGlnvyTqlEd2Bt4w0D9rf1VVfcUHha9qzoIK4eWVmSGN eworrc1+uI+5NKComu+ZjO5haEQBcMVQ+bW5SbMJkYfEVqahb97K6RGBg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdehiedgfedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnhepkeeluddvlefhieelfefggffhffektdehleelgfdugfdvgeekjeejuddthe ehgfeunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep vhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Wed, 29 Mar 2023 06:44:25 -0400 (EDT) Date: Wed, 29 Mar 2023 11:44:22 +0100 From: void To: freebsd-arm@freebsd.org Subject: Re: git takes ages after fetching ports in the resolving deltas stage Message-ID: Mail-Followup-To: freebsd-arm@freebsd.org References: List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-3.29 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; MID_RHS_NOT_FQDN(0.50)[]; NEURAL_SPAM_SHORT(0.41)[0.413]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.26]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.26:from]; RWL_MAILSPIKE_GOOD(-0.10)[66.111.4.26:from]; TO_DN_NONE(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_FROM(0.00)[f-m.fm]; RCVD_COUNT_THREE(0.00)[4]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; FROM_HAS_DN(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4Pmjpy4xKbz40kq X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On Wed, Mar 29, 2023 at 06:29:59AM +0100, void wrote: >Hello arm@, > >Lately I'm finding that git is taking up to 10 minutes in the 'resolving deltas' >stage when fetching ports. > >I'm thinking maybe the git parameters I'm using are suboptimal. Mentioning this >here because the time taken is really apparent on relatively slow hardware >like the rpi4. This machine uses 'git -C /usr/ports fetch --ff-only -q' to >refresh the local ports tree. Should it be using something else? > >The ports tree was initially fetched with >'git clone ssh://anonssh@git.freebsd.org/ports.git' Some figures: rpi4b on stable/13-n254900-a836dce6d085 8GB ram, dev.cpu.0.freq: 2100 /tmp is a tmpfs. usb3-connected hd, zfs updating ports tree with git -C /usr/ports pull --ff-only git pull --ff-only started on Wed Mar 29 10:56:06 BST 2023 git pull --ff-only completed on Wed Mar 29 11:01:17 BST 2023 git in state of 'uwait' in top [00:01:04] Inspecting ports tree for modifications to git checkout... most of the time in uwait, then zio->i [00:08:59] Ports top-level git hash: 5f32c6225 so, 7 mins 55s from poudriere starting inspecting the ports tree to completing it. Is this expected? have only noticed the delay recently. --