all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Joram Schrijver <i+guix-devel@joram.io>
Cc: guix-devel@gnu.org
Subject: Re: guix-daemon hitting systemd TasksMax
Date: Sat, 16 Apr 2016 12:14:38 -0400	[thread overview]
Message-ID: <20160416161438.GB9412@jasmine> (raw)
In-Reply-To: <1460812335.1088225.580600441.5A60AF4E@webmail.messagingengine.com>

On Sat, Apr 16, 2016 at 03:12:15PM +0200, Joram Schrijver wrote:
> I am running Arch Linux, also with systemd 229. It doesn't look like
> Debian applies any patches to systemd, so our installations should
> pretty much be the same.
> 
> Perhaps the limit is only reached during the build process of some
> specific packages?

`guix pull` usually doesn't build any packages, but sometimes it does
need to. My (limited) understanding is that it sometimes needs to build
(or download) updated dependencies of Guix itself.

Do you think the number of "Tasks" would increase with more cores? I
only have 4 cores on my machines. Maybe if you had more, the builders
spawned by your guix-daemon would run more tasks as a consequence of
using all the cores.

I think there are other Guix people on Debian testing. I wonder if they
will hit this issue, too.

  reply	other threads:[~2016-04-16 16:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14 23:37 guix-daemon hitting systemd TasksMax Joram Schrijver
2016-04-15 14:35 ` Efraim Flashner
2016-04-16  1:29 ` Leo Famulari
2016-04-16 13:12   ` Joram Schrijver
2016-04-16 16:14     ` Leo Famulari [this message]
2016-04-16 22:46       ` Ludovic Courtès
2016-04-18 20:33         ` Leo Famulari
2016-04-18 20:42           ` Joram Schrijver
2016-04-19 15:57             ` Ludovic Courtès
2016-04-20  1:20               ` Leo Famulari
2016-04-25 21:37                 ` 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=20160416161438.GB9412@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=i+guix-devel@joram.io \
    /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.