From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Brett Gilio <brettg@posteo.net>
Cc: 38649@debbugs.gnu.org
Subject: [bug#38649] [PATCH] Parallelize `guix package`
Date: Tue, 17 Dec 2019 15:34:31 +0100 [thread overview]
Message-ID: <bc3229e1ac6f2e86ff90c2158287275ad8e6686c.camel@student.tugraz.at> (raw)
In-Reply-To: <6dd517ad-639d-4932-be9c-2acbd889d1ed@localhost>
Am Dienstag, den 17.12.2019, 14:20 +0000 schrieb Brett Gilio:
>
> Dec 17, 2019 8:19:14 AM Leo Prikler :
>
> > Hi Guix!
> >
> > Yesterday I had an interesting conversation on IRC about the
> > behaviour
> > of multiple `guix package` processes running in parallel.
> > Specifically, when two transactions target the same profile
> > (usually
> > /var/guix/profiles/per-user/$USER/guix-profile) at the same time,
> > one
> > of them will fail to claim the lock and abort. 0001 makes it so
> > that
> > the process waits for the lock. 0002 makes it so that packages
> > specified via -i can be built in parallel.
> >
> > Regards,
> > Leo
> >
>
> Can we extend this to include things like environment --ad-hoc?
`guix environment` does not claim any locks, so it does not suffer from
the problem that this patch tries to address. Perhaps my wording was
bad: By "can be built in parallel", I meant that if one starts two
processes, e.g. `guix install emacs` and `guix install ffmpeg`, emacs
and ffmpeg are built in parallel. This does not mean, that
dependencies of emacs are built in parallel – for that you'd have to
dig closer to the core.
Regards,
Leo
next prev parent reply other threads:[~2019-12-17 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 14:18 [bug#38649] [PATCH] Parallelize `guix package` Leo Prikler
2019-12-17 14:20 ` Brett Gilio
2019-12-17 14:34 ` Leo Prikler [this message]
2019-12-17 14:38 ` Brett Gilio
2019-12-17 14:32 ` Ludovic Courtès
2019-12-17 15:19 ` Leo Prikler
2019-12-17 15:50 ` Julien Lepiller
2019-12-17 16:16 ` Leo Prikler
2019-12-18 14:37 ` Ludovic Courtès
2021-05-11 14:24 ` Leo Prikler
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=bc3229e1ac6f2e86ff90c2158287275ad8e6686c.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=38649@debbugs.gnu.org \
--cc=brettg@posteo.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.