public inbox for goredo-devel@lists.cypherpunks.ru
Atom feed
From: goredo <spacefrogg-goredo@spacefrogg•net>
To: goredo-devel@lists.cypherpunks.ru
Subject: File descriptor leak
Date: Sun, 8 May 2022 08:22:42 +0000 (UTC) [thread overview]
Message-ID: <00d733a2-d0af-40c0-b091-00f2b39a12f2@spacefrogg.net> (raw)
In-Reply-To: <6a75db3d-7d4e-6921-db74-50bd4b592108@acha.ninja>
You likely run into the same trouble I did before. You can artificially restrict the number of parallel redo-ifchange calls with "xargs -n 50 ALL_ARGS | redo-ifchange" or try to increase the ulimit values for open files.
If you look into the archives, I, too, mentioned this problem. The way goredo is designed, makes it open all prospective fds upfront although with no intention to run as many parallel processes. So the task is to limit the number of arguments a single redo-ifchange invocation sees. The author's stance at the time was to keep the code simple and let the work be done in the redo targets. But I am still in favour of a more conservative approach to opening files of targets that are not immediately run.
–Michael
next prev parent reply other threads:[~2022-05-08 8:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 4:44 File descriptor leak Andrew Chambers
2022-05-08 8:22 ` goredo [this message]
2022-05-08 9:12 ` Andrew Chambers
2022-05-08 11:21 ` goredo
2022-05-08 11:42 ` Sergey Matveev
2022-05-09 0:31 ` Andrew Chambers
2022-05-09 7:10 ` Sergey Matveev