Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #15268

Re: How does this wait -n work to cap parallelism?

From Earnestly <zibeon@googlemail.com>
Newsgroups gnu.bash.bug
Subject Re: How does this wait -n work to cap parallelism?
Date 2019-07-29 20:02 +0100
Message-ID <mailman.187.1564426959.1985.bug-bash@gnu.org> (permalink)
References <20190729181242.GB2032@teapot> <20190729183848.GE1218@eeg.ccf.org> <20190729190233.GC2032@teapot>

Show all headers | View raw


On Mon, Jul 29, 2019 at 02:38:48PM -0400, Greg Wooledge wrote:
> The same happens for my_job 7, and my_job 8.  Each one is preceded by
> a wait -n, so it waits for one of the existing jobs to terminate before
> the new job is launched.

This aspect of the behaviour isn't in question.

Without reiterating too much, the question is about how that cap is
maintained after the 'wait -n' loop only ever experiences a single agent
while 'i' is incrementing, and only after 'i' has exceeded 'nproc' does
the parallelism start.

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread


Thread

Re: How does this wait -n work to cap parallelism? Earnestly <zibeon@googlemail.com> - 2019-07-29 20:02 +0100

csiph-web