Re: [PATCHv4 06/14] run-command: add an asynchronous parallel child processor
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 23, 2015, 18:04 UTC
- Message-ID
- <xmqqlhbxxbai.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <CAGZ79kYaqFRPfRORbknTyez5u0d6_BD0d5wBtAnjSkb4sUBUBA@mail.gmail.com>
Stefan Beller <sbeller@google.com> writes:
Show 8 quoted lines
> I modified the test-run-command test function to start up to 400 processes. > (Most people will use less than 400 processes in the next 5 years), and run > just as in t0061: > > ./test-run-command run-command-parallel-400 sh -c "printf > \"%s\n%s\n\" Hello World" > > The output felt immediate (not slowed down or anything).
I doubt that such an experiment has any value. You are not driving printf in real life.
You are running "git fetch" that are is a lot more heavy-weight. Because once each of them started fully they will be network bound, it is likely that you would want to run more processes than you have core.