From: ludo@gnu.org (Ludovic Courtès)
To: Joram Schrijver <i+guix-devel@joram.io>
Cc: guix-devel@gnu.org
Subject: Re: guix-daemon hitting systemd TasksMax
Date: Tue, 19 Apr 2016 17:57:05 +0200 [thread overview]
Message-ID: <87vb3dzj5a.fsf@gnu.org> (raw)
In-Reply-To: <1461012120.3265374.582525641.595D96A9@webmail.messagingengine.com> (Joram Schrijver's message of "Mon, 18 Apr 2016 22:42:00 +0200")
[-- Attachment #1: Type: text/plain, Size: 476 bytes --]
Joram Schrijver <i+guix-devel@joram.io> skribis:
> Heh, no I'm not. I have to do it with 4 cores + hyperthreading. My first
> `guix pull` did have to build many things though, spawning numerous
> threads in some cases. I eye-sampled the thread counts during one try
> and they were certainly in the hundreds.
Oh, then it could be that it’s a “make -j8” (assuming 2 hyperthreads per
core) for one of the packages that exceeded the limit.
What about this:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 366 bytes --]
diff --git a/etc/guix-daemon.service.in b/etc/guix-daemon.service.in
index 28ef000..c79f867 100644
--- a/etc/guix-daemon.service.in
+++ b/etc/guix-daemon.service.in
@@ -10,6 +10,7 @@ ExecStart=@bindir@/guix-daemon --build-users-group=guixbuild
RemainAfterExit=yes
StandardOutput=syslog
StandardError=syslog
+TasksMax=1024
[Install]
WantedBy=multi-user.target
[-- Attachment #3: Type: text/plain, Size: 50 bytes --]
(Is it the right syntax?)
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-04-19 15:57 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
2016-04-18 20:42 ` Joram Schrijver
2016-04-19 15:57 ` Ludovic Courtès [this message]
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=87vb3dzj5a.fsf@gnu.org \
--to=ludo@gnu.org \
--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 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).