all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Christopher Baines <mail@cbaines.net>
Cc: 33643@debbugs.gnu.org
Subject: [bug#33643] [PATCH] gnu-build-system: Enable xz to decompress in parallel.
Date: Thu, 6 Dec 2018 16:06:53 -0500	[thread overview]
Message-ID: <20181206210653.GA909@jasmine.lan> (raw)
In-Reply-To: <87o99yo382.fsf@cbaines.net>

[-- Attachment #1: Type: text/plain, Size: 671 bytes --]

On Thu, Dec 06, 2018 at 07:38:21PM +0000, Christopher Baines wrote:
> So, if -T was used to compress the data, then it sounds like it'll work
> to decompress it. I guess this adds a little more uncertainty to the
> benefit of this change, as the impact is dependent on the way the source
> data is compressed.

Right. When parallel decompression is implemented, I think we should
enable it in order to get some benefit from upstream tarballs that may
have been created with multi-threaded compression. 

However, we probably won't be able to use the parallel compression
within Guix because it is apparently not deterministic:

<https://bugs.gnu.org/31015>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-12-06 21:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06  7:56 [bug#33643] [PATCH] gnu-build-system: Enable xz to decompress in parallel Christopher Baines
2018-12-06  8:08 ` Christopher Baines
2018-12-06  8:13 ` Leo Famulari
2018-12-06 19:38   ` Christopher Baines
2018-12-06 21:06     ` Leo Famulari [this message]
2018-12-09 14:32       ` Efraim Flashner
2018-12-10 16:24         ` Leo Famulari
2018-12-10 18:48           ` Efraim Flashner
2020-05-13 18:20 ` Christopher Baines
2020-05-13 19:07   ` Efraim Flashner
2020-05-14  7:37     ` bug#33643: " Christopher Baines

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181206210653.GA909@jasmine.lan \
    --to=leo@famulari.name \
    --cc=33643@debbugs.gnu.org \
    --cc=mail@cbaines.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.