From nobody Fri Dec 13 21:19:24 2024 X-Original-To: freebsd-current@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 4Y92KR11r2z5g8Df for ; Fri, 13 Dec 2024 21:19:39 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ed1-f53.google.com (mail-ed1-f53.google.com [209.85.208.53]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Y92KQ5MV9z4ZLs; Fri, 13 Dec 2024 21:19:38 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-f53.google.com with SMTP id 4fb4d7f45d1cf-5d647d5df91so1256098a12.0; Fri, 13 Dec 2024 13:19:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734124776; x=1734729576; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=aGJDmcnL3ejVmlCWWNabI428NoGqgg5eO/YEpnq3vmU=; b=sWiCNz1RAihGqU7e/XxhCGeFPmNjEiY+PcM7huF301JguGulEX45D4+rOlYJYH17jd 86LUdRJMTGPW/yldqQQro/uzTgeFC4D4Y9YN+gxWJGRrEU4MVsB7koNgfvENUZ9x3BJD FrDpheHw1QiN05o3Uif86r/e1bP5Uwv+G+hD8yAPMQ+81vLkMTm3oGKqDwemj/sCkUiS Wn3LbNUwZYrYpVDyLIsLtFsYhrGlbMIcGCd39KzUz1GKkMXuVBGW4dDGBcLHBjUzNfwV Nf41ki68FtP9vFJ7U5h19XqNmjPI+LS1qSFIoZNe6OP7zWqxFKfoAGvczRWhaMNCBkb2 8pIA== X-Gm-Message-State: AOJu0YzHjIH5oqTqJD/vukcS9CVdxHlo99JhVU8DvfAV4gBmKY5BSdal LMWQkz7LvLDoUdWckNW6K8Wv1s1MQcoFs89Lei2J5Tge2hBhiF4Pm2aWi1hIYpjyCWYq0wdcpFm O14S3DmZFRHPNFmsd0SGDu8kUfm7KlQ== X-Gm-Gg: ASbGncuCQEH2IMeAAY5fY5f3iDFsEL9tiDwIRIkgFuzeGuyEXhyPd1mI/4X/p+px/9O cQBd8d0GRSGZ7kXv6Hgpik9/Qt92Fnjbz1nWpmA== X-Google-Smtp-Source: AGHT+IEJ84E82+mv7m1H8w9hy0tgjkt2qEdd0hjVfzV8cEsBOgPsl9d/UWOAOPS7DfHc8T6xluvRGBJEk0/boNSpZqo= X-Received: by 2002:a05:6402:5242:b0:5d0:ee52:353e with SMTP id 4fb4d7f45d1cf-5d63c3c068cmr3199693a12.29.1734124775886; Fri, 13 Dec 2024 13:19:35 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Alan Somers Date: Fri, 13 Dec 2024 14:19:24 -0700 Message-ID: Subject: Re: Switching release media dist sets to .tzst (tar + zstd)? To: Ed Maste Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Queue-Id: 4Y92KQ5MV9z4ZLs X-Spamd-Bar: ---- On Fri, Dec 13, 2024 at 2:16=E2=80=AFPM Ed Maste wrote= : > > I have been reviewing parts of the release artifact build process, > including ISO and memstick images, and came across the distribution > sets (e.g., base.txz, src.txz) used by the installer to populate new > file systems. I=E2=80=99d like to discuss switching these to .tzst (tar + > zstd) compression. > > While I haven=E2=80=99t yet conducted detailed benchmarks comparing zstd = and > xz specifically for this use case, here are some initial > considerations: > > Pros of zstd: > - Faster compression and decompression speeds. > - Aligns with the compression method used for FreeBSD packages. > > Cons of zstd: > - Somewhat larger compressed file sizes. > - Requires updates to tools that interact with distribution sets. > - May have limited availability on some other operating systems (?). > > I have a review open to demonstrate the extent of the change in the > build system & installer: https://reviews.freebsd.org/D48042 > > It might be that this is not worth pursuing, as dist sets will most > likely go away with the migration to pkgbase, but I would like to > discuss and make an explicit decision. We can separately consider > compression on the release media images themselves. > > Feedback Requested: > > Is there support for this idea? Are there objections to pursuing this? > Are there other factors I should consider, especially compatibility conce= rns? Even with a good internet connection, I usually find that downloading the tarballs is slower than decompressing them. So I vote to stick with xz.