all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Parallel (de-)compression
Date: Fri, 04 Dec 2015 15:44:38 +0100	[thread overview]
Message-ID: <87twnyi889.fsf@gnu.org> (raw)
In-Reply-To: <20151202184550.GA5741@debian> (Andreas Enge's message of "Wed, 2 Dec 2015 19:45:50 +0100")

Andreas Enge <andreas@enge.fr> skribis:

> on my relatively slow ARM build machine with relatively fast storage (SSD),
> I notice that often there is an xz process taking 100% of CPU, while there
> is never more than 20MB/s written to disk. For instance, texlive-texmf
> takes a very long time to build and install into the store.

Are you saying that xz-compressing TeX Live to resend it to
hydra.gnu.org is too CPU-intensive?

> Would it make sense to switch to a parallel (de-)compression tool to leverage
> higher numbers of cores? We have pbzip2 already in Guix, which is compatible
> with bzip2.

Bzip2 provides a CPU/compression ratio tradeoff that is not as good as
xz, so I would avoid it.

Another option would be to trade compression ratio for reduced CPU usage
by using, say, ‘xz -2’ or ‘gzip’.

We did something similar in 5ef9d7d to reduce CPU consumption on the
front-end.  Usually it’s much less important to reduce CPU consumption
on the build machines, but your experience seems to suggest otherwise.

Thoughts?

Ludo’.

  parent reply	other threads:[~2015-12-04 22:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 18:45 Parallel (de-)compression Andreas Enge
2015-12-02 18:52 ` Andreas Enge
2015-12-02 19:18   ` Efraim Flashner
2015-12-04 14:44 ` Ludovic Courtès [this message]
2015-12-06 15:31   ` Andreas Enge
2015-12-06 22:21     ` Ludovic Courtès

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=87twnyi889.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    /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.