From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: guix-daemon hitting systemd TasksMax
Date: Mon, 18 Apr 2016 16:33:45 -0400 [thread overview]
Message-ID: <20160418203345.GB26832@jasmine> (raw)
In-Reply-To: <871t65f9zb.fsf@gnu.org>
On Sun, Apr 17, 2016 at 12:46:16AM +0200, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
>
> > 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.
>
> Right, ‘guix pull’ entails a build of Guix using as many cores as
> possible, with one process per core (and I think each Guile has two
> threads, one of which is the signal delivery thread.)
>
> So, if the limit on the total number of threads + processes is 512 and
> you have 256 cores or more (lucky you!), you may hit the limit.
Joram, are you this lucky? ;)
next prev parent reply other threads:[~2016-04-18 20:33 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
2016-04-16 22:46 ` Ludovic Courtès
2016-04-18 20:33 ` Leo Famulari [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160418203345.GB26832@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).