On Thu, Sep 25, 2014 at 19:17:03 +0200, Freddie Chopin wrote:
> On 09/25/2014 04:59 PM, Ben Boeckel wrote:
> > Does the generated script do parallel builds (like I imagine Tup
> > does)? --Ben
>
> I guess that single-threaded compilation is a good baseline anyway - the
> build made by shell script is a reference with "zero overhead", so doing
> a single-threaded build with your tool of choice will give you the
> amount of overhead the processing of build description requires...
>
> Probably a tool winning in single-thread will win in parallel build too (;
Not necessarily. The "decide what to do next" isn't a no-op algorithm.
There may also be bin-packing logic to try and more intelligently
schedule more expensive tasks (something Ninja does not yet do).
An example:
- A takes 1 second
- B takes 2 seconds
- C takes 3
- no dependencies
- run on 2 cores
The best schedule is (--- is 1 second; the task and | represent
setup/teardown time):
1: A---|B------|
2: C---------|
versus:
1: A---|C---------|
2: B------|
--Ben
--
--
tup-users mailing list
email: [email protected]
unsubscribe: [email protected]
options: http://groups.google.com/group/tup-users?hl=en
---
You received this message because you are subscribed to the Google Groups
"tup-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
